Back Forward Landing Pages Process & Rules category — Work Management page —
Field Level Auditing tab


Access

The Work Management page contains the Field Level Auditing tab. Your application can track, in work item history, the values of a sensitive property. For an example, see PDN article 26135 How to track changed values of work item properties using the Field Level Auditing tab.

Use the Field Level Auditing tab to identify properties you want to track for changes on a work item.

Field level auditing uses a data transform named pyTrackSecurityChanges. That data transform holds information about which properties are tracked for that work type. If that data transform does not already exist for the work type selected in the Work Type field, the system displays this message: There is no data transform currently defined for the selected work type. Please add a property below to create a new data transform and being tracking for that property.

You do not have to leave the landing page to manually create the data transform. The system automatically creates the pyTrackSecurityChanges data transform for the selected work type when you add a tracked property for the work type, using the list on this landing page.

Category

Page

Process and Rules

Work History

Using the Field Level Auditing tab

One RuleSet version in the RuleSet that the selected work type is based on must be unlocked so that the system can create or update the standard pyTrackSecurityChanges data transform and declare trigger rules that it uses for field level auditing.

To configure auditing for a field:

  1. Select the Work Type of the desired property.

    If the work type does not tracked properties, the system displays a message stating that there is no data transform currently defined for the selected work type, and that by adding a tracked property, the required data transform is created. After adding the first tracked property for that work type, the system creates the pyTrackSecurityChanges data transform for that work type.

  2. Using the Smart Prompt, select the Property you wish to monitor. Details about that property will appear after focus is removed from the Property field.
  3. Click Submit.

    If no pyTrackSecurityChanges data transform or TrackSecurityChanges Declare Trigger rule already exists for the selected Work Type, these two rules are created automatically. If the data transform exists, the data transform is updated to include the new property.

For more information about manually configuring field level auditing, see PDN Article How to audit field-level changes to security rule and data instances.

Field

Description

Work Type Select the class in which the properties you wish to audit are located. The class must be a valid work type.
Property Select the property you wish to audit.
Description Displays the short description of the selected property.
Type Displays the property type.
Class Displays the applies to class of the property.
Definitions landing page
Related topics About Data Transforms
About Declare Trigger rules

UpTools — Process and Rules
UpDesigner Studio — About Landing Pages

Help System home pageHelp Home