Flows
Controlling the volume of generated work item history instances
Flows
|
|
Through changes to a system settings rule and a decision tree, you can control which flow shapes in the flows of your application add to work item history at runtime.
By default, when a flow execution completes processing for most shapes, PRPC automatically adds an instance to the work item history.
Optionally, your application can suppress all automatically-generated work item history records, or only a subset of the default history records, based on the values of a system setting rule and a decision tree.
The standard system setting rule Pega-ProCom.FilterHistory controls whether this feature applies to a specific system, based on the production level. You can copy this system setting rule into your own RuleSet, to alter the settings. Select WRITES_ALL, WRITES_SOME, or WRITES_NONE, for each production level from 1 to 5.
When based on a production level, the WRITES_SOME setting is in force, the system uses rule resolution to find a decision tree named FilterHistory, which controls the individual types of flow processing steps written to history. The standard decision tree Work-.FilterHistory writes history for all types of steps. To determine which work history steps appear for a work type in your application, copy the standard decision table into your application RuleSet with an appropriate Applies To class, and update your copy as desired.
For an example of how modify the default behavior, see the PDN article How to control history instances written to the audit trail.
Execution of the standard Utility activity Work-.AddHistory, and other activities that call the History-Add method for a work item can add instances to work item history. The system setting rule and the FilterHistory decision tables do not affect such additions.
|
audit trail,production level |
|
Atlas — Standard System Setting rules |
|
About audit trails and attachments
|