Support Article

Changes to a property value do not show up in audit log



A work class property is flagged for track security changes, but on click of ‘submit’ the audit is not added for the property’s value change even when the property’s value is changed.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a Flow.
  2. In the flow action change the value of the tracked property via user action.
  3. Configure the flow action post activity to update the pyStatusWork property.
  4. Modify the Work-.pyTrackStatus When condition so that it is evaluated to true.
  5. Run the flow, change the tracked property’s value and hit ‘submit’, check the audit tab of the item.

Root Cause

The Work-.pxTrackStatuses Declare trigger was firing before the pyTrackSecurityChanges trigger. The Work-.pxTrackStatuses trigger fired by updating Status updates the Database first.

Now the pyTrackSecurityChanges tries to get the data of properties that needs to be audited by comparing the clipboard values with Database values.

But as the values are already been updated via pxTrackStatuses trigger the difference in value appears as none and no Property level auditing added.


Perform the following local-change steps:
  1. Separate out the triggers into separate events.
  2. Do a 'Save' in between the two events, updating status and updating the values in the flow action.

Published March 28, 2017 - Updated April 21, 2017

Have a question? Get answers now.

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