About Process Definition

Process Definition in OpsRamp enables the automated execution of sequential tasks triggered by specific events. The visual workflow designer utilizes drag-and-drop functionality and comprises the following key components:

• Start and Stop Events (States): Define the initiation and termination points of the workflow.
• Tasks: Represent individual actions that process data and generate output for subsequent steps.
• Gateways: Serve as decision points within the workflow, directing the execution path based on defined conditions.
• Connectors: Establish the flow of execution between events, tasks, and gateways.

Each component is typed according to its function and includes configurable properties to meet specific automation and remediation requirements. The user interface provides comprehensive tools for workflow creation and modification.

Example

The following process definition and deployment tutorial describes an automated process that periodically checks patching requirements, applies and validates the patch, and sends an email notification to DevOps:

Limitations

The following sections outline key limitations and considerations for Process Definition functionality within OpsRamp.

Limitations of Process Definition 

• A process definition cannot initiate actions on entities created or updated by the same process.
• To prevent infinite loops, individual tasks within a process definition are limited to a maximum of 5 invocations. Subsequent executions of the same task will terminate the process. Terminated processes are viewable under Completed Instances with the Externally Terminated filter applied.

Limitations of Incident Signal Event

The OpsRamp platform does not currently support bulk update operations for process automation. Thus, if you configure “Update Incident” criteria in process automation for the signal start event, the incident type signal event will function and trigger the process. However, if incident is updated from Service Desk > Bulk Update, it will not trigger the process.

Limitations of Script

Whenever you add or update a script parameter from the Automation > Script section, make sure you also update any associated processes configured to use that script. If you miss this step, the process will use the previous script configuration.

Supported Category in Process Definition

Following are the Category supported in process definition:

• Automation
• Patch Management
• Network Configuration

Next Steps

• Add new process denition: To start adding a new process definition, refer to the Add a Process Definition page.
• Manage process definitions: To know how to manage the existing process definitions, refer to the Manage Process Definitions page.