Automatic Steps
An automatic step is a programmatic action that requires no manual interaction. For example, an automatic action might copy a file from one place to another or lock or unlock an asset in a version control system. The step appears in the workflow display; the action is performed when the step is executed.
Each automatic action can take one or more arguments to specify how it will execute. Each automatic action can return exactly one value, from a set of predefined values, describing the result of its execution. There can be multiple transitions out of an automatic action, but in a given run, only one transition can be followed.
WorldServer ships with a set of automatic actions. When you insert an automatic step into a workflow, you are prompted to choose the automatic action from the list of available actions.
- The set of licenses you have installed.
- The SDK sample automatic actions that you have uploaded.
- Any customized actions you have built using the WorldServer SDK. See the WorldServer™ Software Development Kit (SDK) Overview (SDK User Guide.pdf in the doc\Additional Documentation folder of your WorldServer distribution). Consult SDL Professional Services for more information about customizing automatic actions.
Scope of Automatic Steps
- Task Scope automatic actions are executed as soon as a task has completed the previous step.
- Project Scope actions are executed once for all tasks in the project that reach the step. As tasks reach the project scope step, they are blocked until all tasks capable of reaching this step have arrived at this step. A task is capable of reaching this step if it has not yet reached the Finish step or if it has not been canceled.
- Project Group Scope actions are executed once for all tasks in all of the projects in a project group that reach the step. As tasks reach the project group scope step, they are blocked until all tasks capable of reaching this step have arrived at this step. The Block Projects Tasks automatic action is such an action, meaning all tasks in the project group must first reach this step before the action runs.
The scope of the step is defined by the scope of the automatic action used on this step. The scope of the action is programmed into an automatic action by the action developer.