Activities
A process is a set of linked activities that perform specific functions. When you create a process in the BMC Atrium Orchestrator Development Studio application, you can use an unlimited number of activities. All processes begin with the Start activity and terminate with the End activity. The only activity that depends on an external system in order to be used in BMC Atrium Orchestrator Development Studio is the Integration Mapping activity. The following table describes the available activities.
Available activities
Activity | Description |
|---|---|
Represents the beginning of a process When you create a process, the Start activity is automatically placed on the process canvas and it cannot be deleted. All activities in a process originate from the Start activity. | |
Represents the end of a process When you create a process, the End activity is automatically placed on the process canvas and it cannot be deleted. All activities in a process terminate in the End activity. | |
Assigns values to a context item In the individual assignment statements, data can be transformed or appended together. | |
Defines user inputs that will be requested during the execution of the process This activity is used only for process exposed in the BMC Atrium Orchestrator Operator Control Panel. If the process is being run through the BMC Atrium Orchestrator Operator Control Panel, it will ask you for input. If it is being run by some method other than BMC Atrium Orchestrator Operator Control Panel, the user inputs will be supplied with default values, if defined. | |
Creates conditional paths in a process A Join object is automatically added to a Switch activity. | |
Allows iterative processing of data in a process | |
Allows two or more process paths to be executed in parallel | |
Launches a new process asynchronously | |
Performs functions on string, numeric, and date type values | |
Records metrics for a process | |
Suspends a process for a specified amount of time | |
Executes scripts that are written in the activity or called by the activity | |
Executes an action on an actor adapter running on the grid | |
Some adapters, such as the Remedy adapter, support tight integration with processes. This activity interacts with those adapters to quickly map external system data to and from context items. | |
Provides a conditional loop within a process that evaluates for a condition and, based on the condition, perform specified operations. |