Skip to main content

 –

Adding and enabling data masking

Suggest edit Updated on March 16, 2021

A chat interaction, and the resulting history logs, can contain sensitive data such as account numbers, policy numbers, and Social Security numbers. Hide this data and mask it in the transcripts that are shared with a customer service representative (CSR). The sensitive data is masked to ensure that the confidential information is not displayed in interaction scripts or emails and is not stored in a database.

When you add a mask to the interaction scripts, the user-entered values are masked in the configured format, for example XXX-XX-NNNN for Social Security number. You can enable or disable a mask based on your business needs.
  1. In the navigation panel of the Interaction Portal, click Application Tools.
  2. Click the Data masking tab.
  3. To add a new mask, click Add mask.
  4. To add data masking to a specific channel, select the Channel from the list.
  5. If you want to enable the mask, select the Enable this mask check box.
    The Mask enabled column displays a green tick mark that indicates the mask is enabled.
  6. In the add mask dialog, complete the displayed fields.
  7. Optional: If the data entered has special characters, select the Advanced mode check box and enter the validation masks in Validation regex field.
  8. Optional: To test and validate the configuration, enter the sample text in the Test your validation field and click Test.
  9. Click Submit.
What to do next:

To disable an existing mask, select the mask from the list and click the Gear icon. In the Edit mask dialog, clear the Enable this mask check box. The Mask enabled column displays a cross mark that indicates that the mask is disabled.

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us