Discussion
Closed
Tracking the Work object - Audit Requirements
Already the code has been placed in the production and work objects had been created. As part of new requirement, we need to implement and the track the process of each step/actions in E2E process (i.e. Audit requirements). If we implement the new requirement, Do we have chances to capture the each step/action on the existing work object? Please advice.
Posted: 9 years ago
Pegasystems Inc.
Pegasystems Inc.
IN
for existing workobjects - would running reports on histrory class helps?
for new work objects -
- Audit can be enabled from Flow Action rule form available under security tab.
- by leveraging OOTB decision tree 'FilterHistory' the audit notes can be customized. (Please see the history tab of the rule form)
- method History-Add can be used in Activity rule forms to log the interaction.
- reports can be created on History-<Work Class> to enable case history information.
- field level auditing or a declare onChange event with a custom audit activity may also work...
- also please refer: https://community.pega.com/sites/default/files/help_v71/procomhelpmain.htm
- having exposed columns in history table helps in performance (with no blob column)
- also please refer: RULE-OBJ-ACTIVITY WORK- PYADDWORKHISTORYDEFAULTS