We have requirement to track changes in the field level auditing. We have implemented the changes but business requirement to track multiple changes to be identified by the Unique ID.
I have case created with 2 followups, as per filed level audit, I can track which field value has been updated / modified . Suppose, I made the changes to the follow up 1 for the fields ( Name and No) , the it will display the values in the field history as Old Value - AAAA and new Value - BBBB . Since Unique id will not change we can't keep track of it as part of field level audit extract.
Here I have attached 3 files for reference.
I have FieldAudit csv - Where it has all extract for fieldlevel audit
another file with old value and 3rd file with New value. But business is expecting, we need to track the unique id in old and new files as well to see what value has been changed for which unique Id.
Please share your thoughts on how to populate the unique ID as part of field level audit extract.
***Edited by Moderator Marissa to update Support Case Details***
Thank you for sharing your idea here in the Pega Collaboration Center (PCC)!
I have submitted this idea on your behalf in our internal system for feature enhancements and updated your post with the associated FDBK-ID. You can take this ID to your Account Executive for next steps.
Snapshot Design pattern as an alternative to field-level auditing.
I have a client where the requirement is to track all field level changes for auditing change history. After a deep dive with the business on the requirement, I learned there were very specific activities in the case journey where changes needed to be tracked. Also, the requirement was to reset the metadata to an earlier state (aka version).
The approach I took was to create a metadata snapshot design pattern. The implementation approach employed a top-level case page property (enterprise data class), a data table, an editable data page (page list), and an activity to save the page when required. The unique identifier was configured at the class level - Autogenerate UID.
When a snapshot was required, the property page was added to the data page list. On save, the snapshots were persisted. The data page can be reconstituted, as needed, with the snapshot history.
The snapshot design pattern also addresses performance issues for high volume conditions, where field-level auditing may be resource greedy.