Enabling security auditing for a data class or rule type
You can record changes for single values and aggregate properties when you enable security auditing.
To enable security auditing for a data class or a rule type, complete the following steps.
- In Dev Studio, create a data transform named
pyTrackSecurityChanges with an applies to class equal to the class
you want to audit.
Note: Examples with this name are provided as standard data transforms for tracking changes to access groups, operator ID instances, Access of Role to Object rules, flows, case type rules, and application rules. You can save copies of these standard data transforms into your ruleset and update the list of properties to be tracked.
- On the Definition tab, in the Action field, select Set.
- Specify the property in the Target field.
- For value list or value group properties, enter a numeric index to identify one value.
- For page mode properties, enter a reference to a single-value property within the page structure.
- In the Source field, enter a word or phrase that will be displayed on the History Details section.
- Click Save.
- Create a Declare Trigger rule named TrackSecurityChanges. The Apply to (class) field and Add to ruleset field are filled out automatically, but can be changed if needed.
- Optional: Leave the Value column blank for a row to apply custom text from a field value rule.
- On the Trigger tab, in the Trigger when an instance is field, click Save.
- In the Trigger activity section, in the Name field, select TrackSecurityChanges for the activity name.
- In the Execute field, click Immediately.
- Click Save.
- Optional: Test the feature by changing a rule or data instance and review the history.
Previous topic Tracking and auditing changes to data Next topic Customizing the memo text for an audited rule