| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
All Operations that can be added into a workflow are out-of-the-box. For a complete list, refer to the section on Out-of-the-box Automation Operations and Workflows below below.
Step 3: Update Service Configurations
...
| Term | Definition | Create New Allowed | Update Allowed |
|---|---|---|---|
| Operation | These are out-of-the-box operations you can use to automate typical IT tasks in your organization. | No | No |
| Workflow | Workflow is a sequence of operations which perform a definitive set of tasks. For example, you can create a workflow where you have the first operation to add a new user to your Active Directory and after this a second operation to update the worklog of your ITSM ticket. This sequence of operations is called a workflow. | Yes | Yes |
| Service Configurations | In order to execute a workflow, the system will need some configurations such as how to connect to the system where the automated task will be executed. For example, when trying to add a user to Active Directory (AD), the Automation system may need parameters such as AD server details, username, password, and more. You can store these configurations under the Service Configurations, which are used during the execution of a workflow. | No | Yes |
| Input Parameters | These are primarily used when integrating either ISM or Luma with Automation. When you want to initiate an Automation Workflow from an ISM ticket or Luma conversation, you might want to pass a few inputs into the workflow from the ticket or conversation. For example, when adding a new user to Active Directory, you might store the Login ID of the new user in the ticket, and this value is then passed from ticket to Automation Workflow. These are known as input parameters. | Yes | Yes |
| Service | When a workflow is published along with a set of Service Configurations and Input Parameters, it is exposed as a Service. An administrator can invoke a service into a ticket workflow. | Yes | Yes |
...