Workflows (JOBP)
Workflows are one of the key executable objects. Workflows serve as containers for objects that must be executed in a specific sequence and with specific parameters. An object that is inserted in a Workflow is called task. A Workflow can also be embedded in another Workflow. By linking the tasks in a Workflow, you establish the sequence of the executions. Thus, the tasks in a Workflow have a predecessor (the previous task in the sequence) and a successor (the next task). Workflows also have a START and an END node. You design them in the Workflow editor on the Workflows definition page.
A Workflow and its tasks have a parent/child relationship. The Workflow has its own properties, which its tasks inherit. However, the tasks also have their own properties, which can override the definitions in the Workflow.
The sequence of the tasks in the Workflow is part of the Workflow logic. However, you can set other parameters that contribute to build that logic. Some of the properties that you can define in the tasks also play an important role to decide when they are executed.
Types of Workflows
Automic Automation for AIOps lets you create the following types of Workflows:
AIOPS
Remediation Workflows that contain pre-configured attributes. These attributes connect and synchronize them with the alarms and with the processes that they remediate. For more information, see Remediation Workflows.
FOREACH
These Workflows represent loops. They repeat one or more tasks several times depending on the defined loop conditions. ForEach Workflows cannot be modified at runtime.
IF
These Workflows represent IF statements. An IF Workflow contains two branches (True, False) to which you can assign tasks. You define a condition in the START node that determines which branch should be processed. IF Workflows cannot be modified at runtime.
The structure of IF Workflows is predefined and cannot be modified; you can only add tasks to one of the branches and arrange them in series. If you need more complex structures, you must embed other Workflows.
IF Workflows do not admit external dependencies
STANDARD
You can add, order, and link tasks in a standard Workflow as you need. Active or stopped STANDARD Workflows can be modified at runtime.
Note: ForEach and IF Workflows do not support bulk operations.
See also: