Masking Sensitive Data in PeopleCode Trace File

Prior to this release, PeopleCode trace files displayed the value of any record field including passwords, sensitive data, or personally identifiable (PII) data through PeopleCode operations, such as variable assignments, function parameters and other operations. From this release, PeopleTools enables you to prevent displaying passwords and sensitive or PII data in PeopleCode trace files.

Applications use the Data Privacy Framework to identify and mark applications-owned record fields as sensitive or PII data. For a description on using data privacy framework, see "Understanding Data Privacy" in PeopleSoft HCM Enterprise Components online help.

PeopleTools does not have access to the Data Privacy Framework provided by applications. Therefore, for PeopleTools-owned record fields, PeopleTools provides the Do Not Trace Value check box on the Record Field Properties dialog in Application Designer. Select this check box to identify and ensure proper masking of passwords and any potential sensitive or PII record fields owned by PeopleTools. However, Oracle recommends that application developers and customers mainly use the Data Privacy Framework and use the Do Not Trace Value check box in rare situations.

See Application Designer Developer’s Guide: Setting Record Field Use Properties.

When you select the Do Not Trace Value check box for a record field or identify a record field as sensitive or PII through Data Privacy Framework, the value of the record field is masked with a single asterisk (*) on the PeopleCode trace file.

To unmask the values of a PeopleTools-owned record field, deselect the Do Not Trace Value check box. To unmask application-owned record fields, refer to the documentation on Data Privacy Framework.