PredefinedDecisionHandler

Description

The PredefinedDecisionHandler is used to control the process. For XOR gateways, the outputs that the process flow should use can already be predefined at the start of a process. All XOR gateways that use the same variable in combination with this ActionHandler behave according to the first decision. This can change the critical path in a process (more information about the critical path can be found here: Critical Path Method (CPM))

Klasse

com.dooris.bpm.actionhandler.PredefinedDecisionHandler

Parameters of XOR Gateways

Parameter	Default Value	Description	Valid Examples

Parameter	Default Value	Description	Valid Examples
`variableName` MANDATORY	N/A	Name of the process variable, based on its value the process flow is predetermined.	`myVariable`
`defaultTransition`	N/A	This parameter determines which process path is selected when the process variable is not defined.	`true`

Parameters of the Outgoing Sequence Flows

For each outgoing condition of a sequence flow, there is an output parameter, which consists of the label of the sequence flow (“Name”) and the value of the process variable (“ID”):

Name	ID	Description

Name	ID	Description
`Yes sure`	`yes`	The name corresponds to the label of the first outgoing condition from the XOR gateway. The ID receives the value that the variable takes at the start of the process, so that this path is automatically executed in the process flow.
`Probably not`	`no`	The name corresponds to the label of the first outgoing condition from the XOR gateway. The ID receives the value that it takes at the start of the process, so that this path is automatically executed in the process flow.

Example

The use of the PredefinedDecisionHandler is explained below using a fictional process for manufacturing different lamps.

Either floor lamps or desk lamps are produced in the manufacturing process. With the PredefinedActionHandler, the type of lamp to be manufactured is already determined in the Smartform at the start of the process. Depending on the type of lamp, the process flows and the critical path (CPM) differ.

To ensure the process always follows the course corresponding to the lamp type selected at the beginning, the PredefinedDecisionHandler must be set up at each XOR gateway “Lamp type?” as follows.

Parameter	Description	Example

Parameter	Description	Example
`variableName` MANDATORY	Name of the process variable, based on its value the process flow is predetermined.	`lampenart`

Name	ID	Description

Name	ID	Description
`Floor lamp`	`Stehlampe`	The name corresponds to the label of the first outgoing condition from the XOR gateway. The ID is assigned the value `Stehlampe`, which the variable `lampenart` can take at the start of the process.
`Desk lamp`	`Schreibtischlampe`	The name corresponds to the label of the second outgoing condition from the XOR gateway. The ID is assigned the value `Schreibtischlampe`, which the variable `lampenart` can take at the start of the process.

Afterwards, the process can be deployed and the corresponding Form created in the Form Designer. To implement this example, only a selection field is needed. In this field, the type of lamp to be produced and the process flow to be used are defined.

After publishing the workflow and the associated Form, a test process can be started. In the following example, a floor lamp is to be produced. For this, “Floor lamp” is selected as the lamp type in the selection field at process start, and then a new process is started by clicking the “Start process” button.

In the “Activities” tab for the newly started process, it is evident that the activities required for the production of a desk lamp are excluded from the critical path calculation.