Introduction to Process Definition
Process definition permits you to define a sequence of tasks to run automatically. Starting with a triggering event such as a timer, signal, or a generic start event, you can describe sequential tasks in a workflow that handles the event. As an 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:
The process definition user interface (UI) provides drag-and-drop functionality to visually define the workflow. Key workflow visualization components include:
- start and stop events, or states
- tasks to process the event and produce data for downstream processing
- gateways as decision points in event processing
- connectors to connect events, tasks, and gateways
Each component class is typed according to the kind of action it performs, with properties for customizing the workflow to meet automation and remediation requirements. The UI provides a rich set of operations to create and edit workflows.
NoteProcess won’t trigger on Scheduled Maintenance, Correlated and Obsolete alerts for Alert Signal Start events.
Limitations of Process Definition
The following are some limitations in process definition execution to avoid loops:
- We can not invoke Process Definition on entities that are created or updated by Process.
- If the user configured any loop within the Process Definition, as shown in the figure below. We added a restriction at the Task Level and a particular task will invoke only 5 times, if the same task comes to execution for the 6th time, stopping the process. The terminated process will appear in Completed Instances by selecting the Externally Terminated filter.
To start, set up and enable the client for automation and remediation.
Set up the Process Definition
To automate activities using process definition, the partner needs to enable the Remediation and Automation product package for the client. If the client tries to use process definition and the partner is not subscribed to the package or the package is not enabled, the UI displays an error message:
Access Denied! This Partner is not subscribed for this product package.
When you create a client, select the Remediation and Automation package in the Product Package creation step to enable process automation.
If the client is already set up but does not have Remediation and Automation enabled,
- Login to OpsRamp portal.
- Navigate to Setup > Accounts > Clients.
- Click the name of the client you want to enable.
- On the CLIENT DETAILS page, in the PRODUCT PACKAGES section, click Edit.
- Select the Remediation and Automation package.
- Click Finish.
Enable Process Automation at the partner level:
- Navigate to Setup > Accounts > Partner Details.
- Click Edit.
- Click the Add Ons tab.
- Select Process Automation.
- Click Save.
To verify that process definition is enabled for the client, navigate to Automation > Process Automation > Process Definitions. If successfully enabled, the PROCESS DEFINITIONS page permits you to create a new process, edit an existing process, and use advanced functions to manage the process definitions.
Supported Category in Process Definition
Following are the Category supported in process definition:
- Patch Management
- Network Configuration
After you have enabled the Remediation and Automation package for the client, you can perform the following process definition activity:
Refer to the Process Definitions Overview Page to get details of created process.
Refer to the User Interface Elements section to learn more about the options available at each step of the process definition creation process.
Refer to the Process Definition Reference section for more information on process definition components and configuring component properties.