Schema Elements and Icons
|
|
|
Location in Workflow Editor
|
Start Workflow
|
The starting point of the workflow. All workflows contain this element and it cannot be removed from the workflow schema. A workflow can have only one start element. Start elements have one output and no input.
|
|
Always present in the Schema tab
|
Scriptable Task
|
General purpose tasks you define. You write JavaScript functions in this element.
|
|
Generic workflow palette
|
Decision
|
Boolean function. Decision elements take one input parameter and return either true or false. The type of decision that the element makes, depends on the type of the input parameter. Decision elements allow the workflow to branch into different directions, depending on the input parameter the decision element receives. If the received input parameter corresponds to an expected value, the workflow continues along a certain route. If the input is not the expected value, the workflow continues on an alternative path.
|
|
Generic workflow palette
|
Custom Decision
|
Boolean function. Custom decisions can take several input parameters and process them according to custom scripts. Returns either true or false.
|
|
Generic workflow palette
|
Decision Activity
|
Boolean function. A decision activity runs a workflow and binds its output parameters to a true or a false path.
|
|
Generic workflow palette
|
User Interaction
|
Allows users to pass new input parameters into the workflow. You can design how the user interaction element presents the request for input parameters and place constraints on the parameters that users can provide. You can set permissions to determine which users can provide the input parameters. When a running workflow arrives at a user interaction element, it enters a passive state and prompts the user for input. You can set a timeout period within which the users can answer. The workflow resumes according to the data the user passes to it, or returns an exception if the timeout period expires. While it is waiting for the user to respond, the workflow token is in the waiting state.
|
|
Generic workflow palette
|
Waiting Timer
|
Used by long-running workflows. When a running workflow arrives at a Waiting Timer element it enters a passive state. You set an absolute date at which the workflow resumes running. While it is waiting for the date, the workflow token is in the waiting-signal state.
|
|
Generic workflow palette
|
Waiting Event
|
Used in long-running workflows. When a running workflow arrives at a Waiting Event element it enters a passive state. You define a trigger event that the workflow awaits before it resumes running. While it is waiting for the event, the workflow token is in the waiting-signal state.
|
|
Generic workflow palette
|
End Workflow
|
The end point of the workflow. You can have multiple end elements in a schema, to represent the different possible outcomes of the workflow. End elements have one input with no output. When a workflow reaches an End Workflow element, the workflow token enters the completed state.
|
|
Generic workflow palette
|
Thrown Exception
|
Creates an exception and stops the workflow. Multiple occurrences of this element can be present in the workflow schema. Exception elements have one input parameter, which can only be of the String type, and have no output parameter. When a workflow reaches an Exception element, the workflow token enters the failed state.
|
|
Generic workflow palette
|
Workflow Note
|
Allows you to annotate sections of the workflow. You can stretch notes to delineate sections of the workflow. You can change the background color of the notes to differentiate between different workflow zones. Workflow notes provide visual information only, to help you understand the schema.
|
|
Generic workflow palette
|
Action Element
|
Calls on an action from the Orchestrator libraries of actions. When a workflow reaches an action element, it calls and runs that action.
|
|
Generic workflow palette
|
Workflow Element
|
Starts another workflow synchronously. As soon as a workflow reaches a workflow element in its schema, it runs that workflow as part of its own process. The original workflow does not continue until the called workflow completes its run.
|
|
Generic workflow palette
|
Foreach Element
|
Runs a workflow on every element from an array. For example, you can run the Raname Virtual Machine workflow on all virtual machines from a folder.
|
|
Generic workflow palette
|
Schedule Workflow
|
Creates a task to run the workflow at a set time, then the workflow continues its run.
|
|
Generic workflow palette
|
Nested Workflows
|
Starts several workflows simultaneously. You can choose to nest local workflows and remote workflows that are in a different Orchestrator server. You can also run workflows with different credentials. The workflow waits until all the nested workflows complete before it continues its run.
|
|
Generic workflow palette
|
Pre-Defined Task
|
Noneditable scripted elements that perform standard tasks that workflows commonly use. The following tasks are predefined:
Basic
■
|
Sleep
|
■
|
Change credential
|
■
|
Wait until date
|
■
|
Wait for custom event
|
■
|
Increase counter
|
■
|
Decrease counter
|
Log
■
|
System log
|
■
|
System warning
|
■
|
System error
|
■
|
Server log
|
■
|
Server warning
|
■
|
Server error
|
■
|
System+server log
|
■
|
System+server warning
|
■
|
System+server error
|
Network
■
|
HTTP post
|
■
|
HTTP get
|
■
|
Send custom event
|
|
|
Basic, Log, and Network workflow palette
|