Skip to main content

Personal data restrictions for GDPR

Suggest edit
Updated on June 30, 2021

The General Data Protection Regulation (GDPR) imposes strict requirements for protecting personal data. When you develop Pega applications, you can restrict personal information from certain functions. You can restrict the access to personal information from internal and external users by using access groups.

Function restrictions

Pega Platform uses instances of the function restrictions class (ClientData-FunctionRestrictions) to store the restrictions on the database. Function restrictions are unique by client ID and application name. If no restrictions are requested by a customer, there are no instances.

When a customer requests restrictions, a function restrictions instance is created. The instance specifies each function in your application, and within each function, each channel where functions can be used. For each function and channel, the instance defines whether that function can be executed. A customer can also request to update or delete function restrictions.

You can view the detailed specification for this REST API in the Pega API specification under the Data Privacy category.

For example: For example, John Doe, a customer included in your MyCRM application, does not want to receive marketing phone calls. The function restrictions for John Doe are shown in the following example:

ClientID: JohnDoe Application: MyCRM

Function: Billing
  • Channel: Email Is Restricted? No
  • Channel: Phone Is Restricted? No

Function: Marketing

  • Channel: Email Is Restricted? No
  • Channel: Phone Is Restricted? Yes

Function restrictions data transform

You customize the pyClientRestrictedFunctions data transform to define the functions and channels that are used by your application and their default restriction values. For sample code, refer to the pyClientRestrictedFunctions data transform that is in the Pega-RulesEngine ruleset.

When rule

The function pzIsFunctionRestricted identifies when a function is restricted for an app, client, function, and optional channel. You create a when rule that calls this function, and you invoke the when rule at the appropriate place in your application so that the function restrictions take effect. For example, the when rule can be used when calculating the next best action or when rendering a section of the user interface so that John Doe does not receive marketing phone calls.


Function restrictions are stored in each application as well as in the GDPR request management application. For auditing and customer communications, report the restrictions that are defined in the GDPR request management application.

The GDPR case management application that is part of Pega Infinity™ CRM and the GDPR Accelerator include case management functionality for managing consent under the Demo-GDPR-Work-ManageConsent class. There is no corresponding case processing in the application.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us