Scripting in workflows

Scripts are configured in the Action form. Action scripts are collected together into Action Sets. When users launch a workflow from an object form, they select an Action Set.

After a user initiates a workflow, the actions within the action set are displayed in the Pending Tasks grid. For each action, there are Event buttons. These buttons have labels that describe the function that the user can perform for that action. Some examples are Edit, Reject, View, and Approve.

The system’s behavior after a user selects one of the buttons is defined by the script functions entered in the Action form. Using the Optiva scripting language and Visual Basic .NET provides many ways to control how you do business.

Each action corresponds to one task. So, the Reject, View, and Approve buttons are scripted and enabled in a single action.

For example, when a user clicks Reject, the script for the Reject event is run.

The behavior for each button can vary for different types of workflows. What happens when a user clicks Complete in one workflow can be different than when another user clicks Complete in a different workflow.