OperatorID audit log incorrect
User complains that when they add a second workbasket on Work tab of OperatorID page, history shows that the second workbasket is added to WorkBasket 1.
When user removes the second workbasket on Work tab of OperatorID page, history shows both the first Workbasket and second workbasket are removed.
Incorrect audit log records.
Steps to Reproduce
1- Create a Data Transform and a Declare Trigger following the steps defined on https://pdn.pega.com/sites/default/files/help_v719/procomhelpmain.htm#howto/howto2/enablesecurityaudit.htm%3FTocPath%3DSecurity%7C_____8.
2- Add pyWorkBasketList(1).pyWorkBasketName and pyWorkBasketList(2).pyWorkBasketName for the Data Transform and the Declare Trigger.
3- Add two workbasket on Work tab of OperatorID page.
4- Remove the workbasket on Work tab of OperatorID page.
5- Check Audit log (history) of OperatorID page.
The issue is in the change tracking for the field level auditing. The logic in the utility functions are not honouring the scenario well. This would need thorough analysis and design considerations given the complexity level of the changes. Workbasket 1 come up twice because the user configured 2 steps in the data transform because of which the audit log is being executed twice. The data transform will be called upon for each new/updated entry, and so duplicacy in audit.
Remove the second step in the data transform "pyTrackSecurityChanges" and update the value in step 1 from Workbasket 1 to Workbasket (remove 1), then the audit log will be tracked properly.
Published February 12, 2016 - Updated October 8, 2020
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.