Currently, in our Complaint Registry, we have to “tag” complaints either as standard or critical, depending on the criticality of the complaint.
The challenge is that we can’t see who added a tag if one is missed, and there’s no audit trail showing when tags were added or modified.
I’m curious to know whether Pega can support tracking this. If so, how could we implement an audit trail for tag creation to improve visibility and accountability?
Hi @Briana_P1 : Pega’s built-in Tags are primarily a collaboration feature, and there’s no OOTB end user faced audit trail for tag associations.
That said, tags on cases and in Pulse are stored as instances of the Link-Tag class. You can leverage data from this class to determine who associated a tag with a case.
The limitation is that this design doesn’t track tag deletions. If tracking removals is important, you’d need to use Declarative rules to capture those events and write them to a custom audit log.
Thanks.
Hi @Briana_P1 , as suggested Tags are not immutable data. Actions like this are best captured as explicit steps or data selection. You can consider adding a simple radio button plus field level audit on the data field.