Rule-Based Workflow: Technical Details
This document explains how the rule-based workflow works by describing the workflow template of the rule-based workflow and how this workflow template of the rule-based workflow uses the BRFplus application of a particular change request type.
We deliver the standard workflow template WS60800086
for the rule-based workflow. This workflow template consists of the following steps:
Start Workflow
An instance of the rule-based workflow template is started when a user submits a change request of a type that has the rule-based workflow template assigned. The same workflow template is also used to create sub-workflow instances for parallel processing.
Determine Change Request Type
The system determines the change request type; for example, Create Material
or Change Material
and stores the change request type in the workflow container.
Check Assignment of Processor to Workflow
The system checks whether a processor is already assigned to the workflow, for example, the current workflow instance is a sub-workflow that was started for parallel processing.
If a processor is not yet assigned, the system launches BRFplus. The BRFplus decision tables for the change request type are used to find the next step, the process pattern, and the agents, based on the previous step and action. If the current workflow instance is the main workflow, the system also refreshes the status of the change request.
Determine Whether Single Processing or Parallel Processing is Configured
The system determines the number of configured agent groups of the current change request step. An agent group can consist of a single user or multiple users. For example, it might be necessary that users in the purchasing department and users in the accounting department should able to approve the change request in parallel.
If more than one agent group is found, parallel processing is configured and the system proceeds as follows:
The system creates multiple workflow instances of the WS60800086
template: one for each agent group. These sub-workflows run in parallel.
As soon as all subworkflows are completed, the BAdI: Handling of Parallel Results in Rule-Based Workflow
in MDG Customizing under is called in order to merge the results of the parallel subworkflows into one result and, based on those results, determines the next step of the change request process.
Branch by Process Pattern
Based on the determined process pattern, the workflow branches into one out of several basic operations of the rule-based workflow.
For more information, see Process Pattern
Check Workflow Completion
The system checks whether the process pattern was 99
Complete (Sub-)Workflow
.
If this is the case the system completes the workflow.
If this is not the case the system returns to step 3 and starts again.