Support Article
Security auditing for properties in embedded pages or page group
SA-22121
Summary
User enabled Security Auditing to monitor a few properties in Data-Admin-Operator-ID. It works fine for single value properties and for page lists. However, there are problems with a property in an embedded page group property and with a property in an embedded single page property.
The auditing triggers for those two properties, but the entry in the history log doesn't have the expected value. The field values for TrackSecurityChange_Add, TrackSecurityChange_Change and TrackSecurityChange_Remove are not looked up and used in the log entry as expected.
Instead of "Geändert Email von [email protected] nach [email protected]" we see "TrackSecurityChange_Change [email protected] [email protected]".
Error Messages
Not Applicable
Steps to Reproduce
1. Add a page group property to Data-Admin-Operator-ID, for example pyAddresses of class Data-Address
2. Create a data transform in Data-Admin-Operator-ID called pyTrackSecurityChanges. Set .pyFirstName to a blank value and set .pyAddresses(Email).pyEmailAddress to a blank value
3. Create field values for .pyFirstName called TrackSecurityChange_Add, TrackSecurityChange_Change and TrackSecurityChange_Remove. Add some label text there
4. Create the same field values in Data-Address for .pyEmailAddress
5. Create a declare trigger in Data-Admin-Operator-ID called TrackSecurityChanges, executed when object is saved, calling activity TrackSecurityChanges immediately
6. Open an operator id and change first name and emaill address in .pyAddresses.
7. Save operator id.
8. Check history. While entry for .pyFirstname contains the labels entered in the field values, the entry for .pyAddresses(Email).pyEmailAddress doesn't. It contains the field value names instead.
Root Cause
The Field Values for .pyEmailAddress entries, and the Embedded Single Page Properties were not located in the correct class.
Resolution
Perform the following local-change: Create the .pyEmailAddress Field Values for Field Level Auditing entries in the Data-Admin-Operator-ID class.
The embedded Single Page properties must be located in the Data-Admin-Operator-ID inheritance path.
Published April 15, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.