Workflow step summary

The workflow process consists of the following steps (or states). The table lists the steps in the approximate order in which they occur in the workflow script. A designation of structural indicates that these steps are mandatory and that Studio inserts them into the workflow process automatically. Studio marks the structural steps with brackets (<...>) to indicate that they are actually XML elements. Some of the structural elements have no visual representation within the workflow diagram itself. You can choose them only from the workflow outline.

Step	Script contains	Description
<Context> Workflow Element	Exactly one	Structural. Element for defining symbols used in the workflow. Generally, you define a symbol to use as convenience in defining objects in the workflow path. For example, you can define a symbol such that inserting “Cancellation” into the text workflow actually inserts “Workflow.PolicyPeriod.Cancellation”.
<Start> Workflow Element	Exactly one	Structural. Element defining on which step the Workflow element starts. It can optionally contain Gosu code to set up the workflow or its business data.
AutoStep Workflow Step ActivityStep Workflow Step ManualStep Workflow Step MessageStep Workflow Step	Zero, one, or more	A step is one stage that the Workflow instance can be in at a time. There can be zero, one, or more of any of these steps, in any order. Each of these steps in turn can contain one or more of the following: Any number of `Assert` code blocks for ensuring the conditions in the step are met. An `Enter` block with Gosu code to execute on entering the step. Any number of Event objects that generate on entering the step. Any number of Notification objects that generate on entering the step. An Exit block with Gosu code to execute on leaving a step. Several of these steps can contain other, step-specific, components: An `ActivityStep` can contain any number of `Activity` steps that generate on entering the step. An `AutoStep` or `ActivityStep` can contain any number of `GO` branches which lead from this step to another step. A `ManualStep` can contain any number of `TRIGGER` branches which lead from this step to another step, if something or someone from outside the workflow system manually invokes it. (This happens typically through the PolicyCenter interface.) A `ManualStep` can contain any number of `TIMEOUT` branches that lead to another step after the elapse of a certain time.
Outcome Workflow Step	One or more	A specialized step that indicates a last step out of which no branch leaves.
<Finish> Workflow Element	Zero or one	Structural. An optional code block that contains Gosu code to perform any last cleanup after the workflow reaches an Outcome.