You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
It is important for organizations to be able to exactly what exactly happened to their business processes. All decisions that the process engine takes are stored in the Trace Database. This means that a business can inspect years later why a certain case was approved or rejected.
The following actions automatically create an entry in the decision table of the trace database:
Action | Description |
|---|---|
| Task opened | A new instance of an ad-hoc task is created. If available, log the decision that was made to open this task. |
| Task closed | An instance of an ad-hoc task is closed when the precondition will turn into FALSE. If available, log the decision that was made to close this task. |
| Split nodes | A process has passed a splitnode and has taken one or more paths based on one or more decisions. Log the decision that was made |
| Timer expired | When a timer event expires, the logic should be stored as a decision. Both in sequence and ad-hoc |
| Conditional event evaluates to TRUE | When a conditional event evaluates to TRUE the logic should be stored as a decision. Both in sequence and ad-hoc |
For each time a decision is stored the values listed underneath should be stored.
- ID
- Application ID
- Action name
- Task persistency id
- Task instance id
- Case name
- Case instance id
- Decision graph
The decision graph is stores following the XSD specification for the Decision Model and Notation, as defined by the Object Management Group. This specification can be found here: http://www.omg.org/spec/DMN/1.0/Beta1/. OMG defines three levels of conformance. Blueriq follows conformance level 1.
- The functional specification of the mapping from runtime to the XSD can be found here: Traceability
- The functional specification of the mapping from runtime to the XSD can be found here: Traceability
Overview
Content Tools