Flow rules
Controlling the volume of generated work object history
instances
|
|
Through changes to a system settings rule and a decision tree rule, you can control which flow shapes in the flow rules of your application add to work object history at runtime. PROJ-182 5.4
By default, when a flow execution completes processing for most shapes, Process Commander automatically adds an instance to the work object history.
Optionally, your application can suppress all automatically-generated work object history records, or only a subset of the default history records, based on the values of a system setting rule and a decision tree rule.
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 table
rule named FilterHistory, which controls the individual types of flow
processing steps written to history. The standard decision table rule
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 Pega
Developer Network article 
PRKB-25196 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 object can add instances to work object
history. The system setting rule and the FilterHistory decision tables do
not affect such additions.
|
audit trail,production level |
|
Atlas — Standard System Setting rules |