Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Customizing the memo text for an audited rule

Updated on July 1, 2021

You can customize the memo text to provide a more detailed description of the change that was made to a rule or data object. Use field value rules to change the memo text that is displayed on the history details reports for a property.

  1. In Dev Studio, in the navigation panel, click RecordsData ModelData Transform.
  2. Search for the data transform named pyTrackSecurityChanges and open it.
  3. On the Definition tab, leave the Source field blank for the row that sets the property.
  4. Create three field value rules. In the Label field, enter the following values.
    • TrackSecurityChange_Add
    • TrackSecurityChange_Change
    • TrackSecurityChange_Remove
  5. In the Field Name field, for each field value, enter the name of the field where the memo text will be displayed.
  6. In the Apply to (class) field, for each field value, set the class that the data transform applies to.
  7. Click Create and open for each field value.
  8. On the Localized Label tab, in the To field, enter the text to display in the memo field.
    1. In the TrackSecurityChange_Add field value, enter {1} to refer to the new value of the tracked property.
    2. In the TrackSecurityChange_Change field value, enter {1} to refer to the old value and {2} to refer to the new value.
    3. In the TrackSecurityChange_Remove field value, enter {1} to refer to the old value of the tracked property.
  • Previous topic Enabling security auditing for a data class or rule type
  • Next topic Auditing changes to aggregate properties

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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