Posted: 1 Jun 2020 2:22 EDT Last activity: 1 Jun 2020 13:17 EDT
Audit trail requirement
Hello all - We have a requirement for audit trail where customer is expecting all the application fields (There are close to 10K fields) and all system actions (routing, work flow approvals, inbound and out bound notifications, downstream integrations etc) to be audited with custom UIs to display the audit trail. Need to know below..
1 - Is there an OOTB approach for the said requirement?
2 - Will there be any performance impact ?
3 - Given the requirement we have gotten, what would be the best approach to suggest to the customer?
1. I am afraid that there is nothing OOTB in Pega for audit trail that would support 10K properties as you either config it manually in the Case Type (which is hardly doable for 10K), or in data transform which is again impossible for 10K items. So, likely they will need to design some custom logic in onSave trigger to iterate through all the fields and compare if the value changed. As for "routing, work flow approvals, inbound and out bound notifications, downstream integrations etc" - some of those items are covered OOTB (like routing and flow approvals), for others custom logic might be required.
2. It will likely slow down saving of an object a lot as you will need to perform 10K comparisons at least + saving History records. History table also will be growing quickly, frequent archiving will be high desired.
3. I recommended some possible solution in p.1. Also, I would ask the customer why do they need an object with 10K fields in it. Is there any possibilities to split it to smaller cases or completely eliminate some of those fields reducing complexity. With 10K fields in place the process looks too much complicated to me.