Field auditing

https://docs-previous.pega.com/case-management/87/extension-point-field-level-auditing

https://docs.pega.com/bundle/platform-88/page/platform/case-management/displaying-index-keys-properties-field-level-auditing-layout.html#extension-points-for-field-level-auditing-tsk

DT - pyFieldLevelAudit : Example : Append to .pyAuditFields -> set .pyPropertyName "pyID"

Packaging

• A full class of a case type with enabled field-level auditing, for example FLAudit-PegaProjMgmt-Work-UserStory-Epic
• A class group of a class with enabled field-level auditing, for example FLAudit-PegaProjMgmt-Work
• DB table instances of the class 'FLAudit-PegaProjMgmt-Work'

Extension point:

• Create property in FLAudit- class. On the new property form, in the Additional configuration options section, select the Optimize for reporting and Optimize for reporting on descendant classes checkboxes.
• Save as FLAudit-.pySave activity to FLAudit-<WorkPool> class. Refer Param.ContextPage (for WorkPage context)

Declare trigger -> Queue processor

History (History-Add activity method, AddHistory activity, flow connector shape)

Manage case history writes using decision tree : FilterHistory

FilterHistory application setting : WRITE_NONE/WRITE_SOME/WRITE_ALL

WRITE_NONE - All ootb history writes will be skipped

WRITE_SOME - FilterHistory decision table on the casetype class is considered