The Script Task is used to perform an automated activity (which does not require a user to complete a form).
It is typically used to execute an expression or rule.
Configuring a Script Task
- Right-click the Script Task node on the designer canvas.
- Select Properties. — or —
- Double-click the node on the canvas. The General Tab of the Configure Script Task Dialog Box is displayed.
The General tab allows you to name and describe the node.
Process Designer Configuration Options
The following tabs are only displayed in the Process Designer view.
The Data tab displays the node inputs and node outputs for the script task. Typically, script tasks are configured using node outputs.
- Select the Outputs property sheet. Click . The Expression Properties for the node output are displayed.
- Create an expression to perform your scripted action.
- Select an operator from the Operator list. The default value (is stored as) populates a process variable with the data generated by the expression.
- Select the process variable list. All previously-defined process variables with the same data type are displayed.— or —
- If you need to create a new variable to store your Script Task Output, click . The New Process Variable dialog box is displayed. See the Configuring Process Variables help topic for more information on configuring a process variable.
This activity cannot assigned to a user or a group. A task form cannot be configured.
The Scheduling tab allows you to configure the flow activity so that it only starts after certain time-period has lapsed since the last node completed, or start it according to a fixed calendar schedule. You can also set repeated execution for the node.
This tab allows you to select whether this unattended activity runs as the user who initiated the process or as the person who published the process model (the user context). You cannot assign this activity to a user or a group.
- You can configure different escalation events if a task is not completed within a specified period of time.
- Events can be added to a node through the exceptions tab. If any of these events execute, the current process flow is skipped and an exception flow is taken instead. Furthermore, the node in which the event was configured will also not execute.
The Other tab allows you to configure a number of node options including:
- Running multiple instances of a node.
- Setting deadlines by which the task should be completed.
- Deleting Activity Classes (for disk-space savings) or retaining the node data for auditing purposes.
- Whether or not users can step back to this node after it has been completed in an Activity-Chain.