This document explains the elements for creating a start/stop automation at a high level.
...
When creating new start/stop automation procedures, always test on OZSoft tenant first.
Ensure that the prerequisites for Start/Stop automation have been met. This includes the creation of an OS user, granting necessary permissions, configuring web methods, etc. Also, confirm that the user is capable of initiating Start/Stop procedures for both the SAP system and the database at the OS level.
Elements of Start/Stop
Impersonating as OZSoft admin, navigate to Management → Automation → Definition and expand the menus
...
Each step in the workflow represents a process definitionan activity. Inside a process definition, you can modify the following fields.
...
In this example, this verification asks for the status of the SAP system. To specify define this process definitionactivity, you need to add the following:
...
In the example, the criteria is asking if the object’s status id is NOT equal to 40 (which means it’s not ‘In Progress’ and thus is not currently running. If the criteria is true, then it’ll move on to the step to the right. If it’s false, it’ll do the final step and end the workflow.
In other types of criteria, you can about check the system’s class. In this example, it’s asking if the object’s class is from an ABAP system.
...
Adding jobs to the workflow
...