The decision, which path the process should take at a fork in the road, can be made via e-mail. For this, the decision-making employee recieves an e-mail with links, with which the path of the process can be decided.

• Mailnode, which contains the links for decision making
• Tasknode before decision (with named output transition), so that the process waits for a decision rather than jumping ahead
• XOR-Decision, with clearly named outputs
• VariableDecisionHandler on the XOR which considers a particular variable

http://URL of the server/loom-portal/ProcessInstanceManager/setProcessVariableAndSignalProcessInstanceByTransitionName.soap?args[0]=${processInstanceId}&args[1]=variable&args[2]=Ja&args[3]=Entscheidung&args[4]=entscheidung&i=1&uid=eWl0L3BtOnRhc2shbm1vdGlvbg

Parameters of the link:

• args[0]: Process instance ID of the process. This parameter can be used as shown
• args[1]: Variable name, which should be set
• args[2]: Value to be written in the variable. This value corresponds to the name of one of the XOR outputs of the XOR, depending on which output should be taken (in the example : “Yes or No”)
• args[3]: Name of the activity to be signaled (in the example “Decision”)
• args[4]: Technically unambiguous identification of the transition which exits from the signaled activity (in the example “decision”)
• uid: Login data coded for TIM Base64 (mandant/user:password) (see www.tim.taskinmotion.de/loom-portal/helper.htm)

The link ensures that the task will be completed and the process can continue. In addition, the variable being considered by the VariableDecisionHandler is set so the that correct branch can be followed. VariableDecisionHandler in return sends the decision in the right direction.