- 25 Oct 2024
-
DarkLight
-
PDF
Itential Actions for Using Instances
- Updated on 25 Oct 2024
-
DarkLight
-
PDF
The Itential Automation Services Application includes Itential-built Actions. An Action is a reusable operation that enables process analysts to automate ServiceNow platform features without having to write code. These actions need to be incorporated into Flows which are then integrated into other ServiceNow Processes (e.g. Change) via triggers.
These actions have been built to work regardless of the way you are authenticating to Itential. You will notice there are duplicate actions - one for connecting to Itential through a MID Server, and one for connecting directly (without a MID Server). MID Servers are generally utilized when going from a public ServiceNow instance to an instance of Itential that resides in a private customer network.
Itential has provided ServiceNow Actions to coincide with the existing functionalities of an Itential instance. The goal is to make it easy for the end-user who uses both Itential and ServiceNow to perform automations on the Itential instance from the ServiceNow platform.
List of Actions Built for Using Itential Instances
- automation-cancel
- automation-get-metrics
- automation-get-result
- automation-get-status
- automation-get-token
- automation-get-token-oauth
- automation-start-endpoint
- automation-start-manual
- automations-list
MID Server Actions have the same inputs and outputs as the non-MID Server Actions - they just connect through the MID Server defined in the IAP Instances Config Table. All of the MID Server Actions are suffixed by "-midserver", such as automation-start-endpoint-midserver.