Skip to main content

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.

Support Article

Unexpected working of Field-level auditing

KCP-483

Summary


On changing values of properties (of a case type) that have Auditing enabled, Field-level auditing does not immediately record value changes to all properties. However, this works when the Tracer is used.

 

Error Messages


Not Applicable

 

Steps to Reproduce

  1. Create an AuditHistoryCase instance.
  2. Submit the flow action.
  3. Navigate to the screen flow.
  4. Fill in the address values.
  5. Click Save.

 

Root Cause


pxTimeCreated is one of the keys in the Audit history records. If the same pxTimeCreated is passed to two records, then only one of the records is inserted into the database. In the case of audits, pxGetCurrentTimeStampThreadUnique() function computes this timestamp. When two or more properties are committed to the database at the same time (or simultaneous audits), the timestamp is incorrectly computed.

 

Resolution


This feature is implemented in Pega Platform 8.2.3.
Suggest Edit

Published December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us