Data Privacy Framework

The Data Privacy Framework, delivered by PeopleSoft applications, provides the ability to identify and mask personally identifiable information, or PII, and sensitive data, and is implemented through data masking and filtering.

Data Masking

Data masking allows masking of all or some of the data displayed in certain PeopleSoft Pure Internet Architecture page controls. The SetDisplayMask method will replace each character of the displayed field text value with the chosen mask character.

Several PeopleCode methods related to data masking are available. They are described in the PeopleCode API documentation.

Note:

SetDisplayMask works for all page field types with this limitation. You can use SetDisplayMask for long edit text boxes if the field assigned to the long edit box is not a Long Character Data Type.

See Application Designer Developer’s Guide: Using Edit Boxes and Long Edit Boxes

See PeopleCode API Reference: SetDisplayMask method: Field class.

See PeopleCode API Reference: UnSetDisplayMask method: Field class.

See PeopleCode API Reference: CopyDisplayMask method: Field class.

PeopleCode Built-in functions are provided to help decide which fields should be masked.

See PeopleCode Language Reference: IsRecFieldPII function.

See PeopleCode Language Reference: IsRecFieldSensitive function.

Note:

The PII and sensitive designations for a record field are made through the Data Privacy Framework of the PeopleSoft application that delivers the record field. Therefore, PeopleTools does not provide a way for users to directly modify these designations.

Masking can be applied differently for users by implementing several PeopleCode built-in functions.

See PeopleCode Language Reference: IsUserInRole function.

See PeopleCode Language Reference: IsUserInPermissionList function.

See PeopleCode Language Reference: IsPIIandSensitiveForUser function.

Filtering Drop Downs Based on User Attributes

PeopleSoft provides the ability to specify an override prompt table for any record field that already has a prompt table defined.

At runtime, when the Prompt button is clicked, if there is an override edit table assigned to the Record Field being clicked, that override table will be used to determine the result set instead of the defined prompt table.

The following PeopleCode field object properties will be affected:

• PromptTableName

  If the defined Prompt Table has been overridden then this property will return the Override Prompt Table Name instead of the Prompt Table defined on the Record Field in Application Designer.

• SQLText

  If the defined Prompt Table has been overridden then this Property will return the SQL defined in the Override Prompt Table. When this Property is used to replace the SQL text being used at Runtime it will still work as designed no matter whether there is a configured override or not.

View filtering based on Runtime OPRID is already available via the %OprClause Meta-SQL; however, use of this Meta-SQL is restricted to Dynamic Views. All Prompt Override tables must be Dynamic views and must use %OprClause.

Note:

PeopleSoft allows customers to create the Override Prompt Record/view definitions and define the appropriate view SQL by incorporating %OprClause as appropriate. The Override Prompt Table settings and the data will not be comparable or copyable. The customers can propagate their overrides to other database environments.

See PeopleCode Language Reference: %OPRCLAUSE meta-SQL element.