This document explains the elements for creating a start/stop automation at a high level.
...
While you’re creating the process definitionstart-stop workflow, you must take note of the following:
The external variables that
...
are going to
...
be input in the form
The steps that are going to be in the workflow
The workflow’s sequence
...
Each step in the workflow represents a process definition. Inside a process definition, you can modify the following fields
Name: Name of step
Owner: All process definitions in a workflow must have a robot user as owner, otherwise the process won’t run. This robot user must have assigned an OS user that can run sudo commands (for linux) and SQL commands (for Windows)
Work queue:
Command: This is the core and main instruction of the process definition. You can use both Linux and SQL commands for start/stop processes. However, it is important that you manually test the command to make sure it works before creating the process definition in IT-Conductor
...
(por aqui se empieza, primero hay que averiguar que fields/variables/data vas a necesitar
...
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 also includes entering the name and description of the wizard,
...
the owner (usually the admin user of that tenant
...
), the target class (choose execution config), and the form template
...
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 “Input parameters” and “Create process” steps, and change the name, description, process definition, and form template from that wizard’s steps.
...
Dashboards
You may design a dashboard for start/stop automation like the one for OZsoft and add them to the tenant’s main menu if necessary.
...
The Start/Stop automation dashboard for OZsoft has a tile for the Start/Stop Wizards that you can modify by entering the Design Mode (to use the enter design mode you need to use your admin IT-Conductor account, not impersonate the tenant’s admin).
In the You can add a Wizard tile , you select to display a few pre-created wizards to show upfront.
...
The wizard tile contains the following options:
...
Dashboard: Select the dashboard that it belongs it’ll belong to
Title: Name of the tile
Menu item: Here you insert the pre-created wizard items that the tile will showdisplay. The items are inserted inside a saved search which has the object ids of the pre-created wizards. In the saved search, in “Display mode” you may also select how the wizard items will be displayed on the dashboard. how to create a saved search?
...
Row: Select the row where they the tile will be placed
Column: Select the column where the tile will be placed
opciones importantes
-menu item: para insertar un wizard en el dashboard, hay que primero crear el wizard, guardar el object id del wizard en una saved search y llamar a esa saved search desde menu item
(saved search es un predefined search criteria que trae los resultados de una prebusqueda/static object id)
((pregunta: como se crea una saved search?)
en el saved search puedes especificar como mostrar la tile del wizard en el dashboard (puede ser como lista o como cards, o como stream
...
Parameters: Insert the id of the tenant that this tile/dashboard will be associated to