This document explains the elements for creating a start/stop automation at a high level.
Example: OZSoft tenant.
When creating new start/stop automation procedures, always test on OZsoft tenant first.
Elements of Start/Stop
Impersonating as OZSoft admin, navigate to Management → Automation → Definition and expand the menus
Process Definitions
The process definition is the core and the first step of the start/stop process.
While you’re creating the process definition, you must take note of the external variables that you’re going to need to be input in the form.
(por aqui se empieza, primero hay que averiguar que fields/variables/data vas a necesitar
command: previously test the command. make sure it works manually
Se pueden usar commands linux y SQL para start stop
min 34:57
despues de testear el command manualmente, testear en itc
usar variables.
despues de terminar de modificar el command en el process definition, regresar a la form (form template) y asegurarse de que este atrapando esas variables indicadas en el command y en el work queue
work queue: this is where the activity is going to run (en el ejemplo del video, it runs in a linux host). for start stop make sure to select a dynamic work queue
owner: todos los process definitions en un workflow (de start o de stop por ejemplo) tienen que tener a un robot user como owner, si no, no va a funcionar. Y el robot user tiene que tener un OS user asociado tmb. el OS user asociado debe poder hacer sudo commands (para linux).
(preguntar min 37:54 for sap host you need to be able to add the permission for host agent al usuario owner)
Form Templates
To create the form templates you need to have identified the fields, variables, or data that will serve as input parameters for the start/stop wizard.
Chances are that there already exists a form template with the necessary inputs, in that case, you may reuse it instead of creating a new one.
Otherwise, you can duplicate the one with the closest parameters. You can see which variable, app, or class the form is calling on the “Property” column. To edit the template, you can select a row and click on “Modify row.”
Execution Configs
Execution configs are a list of variables that you pre-configure to use in the future, for example, if you’re going to schedule a process to run in the future. Ad-hoc execution configs won’t appear on this list.
Wizard
The wizard in IT-Conductor is a combination of the form template and the process definition. It’s where the user will launch the start/stop workflow.
The creation of the wizard is divided into three steps:
Input parameters: Here, the user will enter the parameters needed to run the workflow. These parameters are specified in the selected form template.
This step includes entering the name and description of the wizard, and the owner (usually the admin user of that tenant).
Create process: In this step, on the “Wizard_Element.Definition” option, you select the previously created process definition
View process: It’ll show you a final view of what the workflow looks like before you save the wizard
Same as with process definitions and form templates, you may copy an existing wizard and modify the name, description, process definition, and form template from that wizard’s steps.
Add Comment