iGrafx Automation Wiki

Often decisions are made in TIM via E-Mail. It could sometimes be desired to be able to make these decisions manually in TIM. For example if the decision-maker, who gets the E-Mail cannot respond. In this component the implementation of decisions via mail and manually are explained.

Activities and gateways that ar needed for implementation:

• Mailnode to the decision-maker
• Task for manually finishing
• XOR Gateway (2x opnening, 1x closing)
• Connection lines
• Start- & Endnode

Actionhandler that are needed for implementation:

• Actionhandler: VariableDecisionHandler
• Actionhandler: ProcessVariableSetter (2x)
• Webservice: setProcessVariableAndSignalProcessInstanceByTransitionName

The Mailnode needs besides the text the links to accept or deny. These are built as follows:

 http://URL of the Server/loom-portal/ProcessInstanceManager/setProcessVariableAndSignalProcessInstanceByTransitionName.soap?args[0]=${processInstanceId}&args[1]=freigabe&args[2]=true&args[3]=Manuelly_deciding&args[4]=release&i=1&uid=eWl0L3BtOnRhc2shbm1vdGlvbg

 http://URL of the server/loom-portal/ can be subsituted by ${baseLink} after [[software:tim:changelog:tim35|TIM Version 3.5]].

Parameter of the links}}

• args[0]: Processinstance ID of the process. This parameter can be taken like this
• args[1]: Variablename which should be set
• args[2]: Value which the varible be set as
• args[3]: Name of the activity which should be signalled (in the example “Manually_deciding”)
• args[4]: Tehcnical unique name of the transtition which follows the signalled activity
• uid: Login data coded for TIM Base64 (client/user:password)

Attention: A link for declining is also needed. Hereby parameter 2 (args[2]) is changed. >Attention: The transition following the activity “Manuall_deciding” needs a technical unique name. In this example “release”.

Activity which is to be signalled when callingthe link. This activity needs a task like for example “Please decide manually”. The transition following the activity needs a technical unique name. In this example “release”.

On the first XOR a VariableDecisionHandler is set with defaultTransition, for the manual descision, to the second XOR. This XOR decides by means of the in the link set variable. Depending on the set variable “Release via Mail”, “Decline via Mail” or “Manual Release” transistion are selected.

Here no actionhandler is needed. This XOR is only reached, if the task “Manually_deciding” is checked by hand and no processvariable is set via the link. If this XOR is reached, a dialogue in TIM appears, in which the processor can decide over the following process sequence. Depening on the decision one of the Scriptnodes are executed.

On the scriptnodes it the manual decision a ProcessVariableSetter set, which sets the variables from link. This is for later documentation of the process sequence.