Scroll export button scope current template-id c9a14909-8f27-452d-bca0-164bee1a9265 caption Download this Page add-on Scroll PDF Exporter
Feature released in SummitAI Service Management (Alps)
Many enhancements are done related to Orchestration to improve the user experience and to make Orchestration more simpler and easier to use. Orchestration (previously, called Runbook Automation or RBA) is now available as a licensed add-on. For more information, see AOrchestration - Licensed Plug-In.
CI drop-down lists now offer auto-complete search option
Previously, the CI fields on the ORCHESTRATION page (Admin > Advanced > Automation > Orchestration > Select the Trigger Name to open the ORCHESTRATION page of the respective Trigger) were selected from the drop-down lists. Now, the CI fields are configured with the auto-complete search option. Using auto-complete search, the users are prompted with relevant words as they type in. The CI fields available in the following tabs offer auto-complete search:
- Step 1 - Configure Criteria tab: CI field
- Step 2 - Configure Actions tab
- Predefined CI field of the CI Type specified as Predefined CI
- Default CI field of the CI Type specified as Dynamic CI
- Select CI field under Configure CI Mapping pop-up page of the CI Type specified as Dynamic CI
| Expand | ||
|---|---|---|
| ||
Figure: Step 2 - Configure Actions Tab: Predefined CI
Figure: Step 2 - Configure Actions tab: Default CI
|
Additional Script status, In-Progress to display the status for running Scripts
Previously, the Orchestration Scripts that were linked to the Incident(s), Service Request(s), and Work Order(s) were executed by the proxy and the status of the scripts was updated from New to Success or Failure. There was no status change when the Script was getting executed. Meaning, the Script status used to change from New > Success/Failure.
A new status, In-Progress is added before Success or Failure status. Now, after the job execution is initiated, the status of the scripts is updated to In-Progress. If one of the scripts is not executed by the proxy within the job completion time, the Script status remains as In- Progress until the script is executed and the status is updated to Success or Failure. Meaning, now, the Script status changes from New > In Progress > Success/Failure.
Quick and easy Parameter configuration with redesigned UI
Earlier, in the Step – 2 Configure Actions tab of the ORCHESTRATION page, when users selected a Scriptfrom the Script Name drop-down list, the Parameters configured for the Script were displayed in the Parameter drop-down field present under the CONFIGURE PARAMETERS section.
To map Script Parameters to a source, users had to select Parameter, Data Source, and Data Value from the respective drop-down lists, and then click SAVE PARAMATER.
If an Orchestration configuration had more than 5 Scripts with each Script having more than 10 Parameters, this was a time consuming process.
Now, when users select a Scriptfrom the ScriptName drop-down list, the Parameters configured to the Script are displayed in a tabular format and users can map the Data Source and Data Value against each Parameter.
| Expand | ||
|---|---|---|
| ||
Figure: Parameter configuration |
Complete Script output
Now, the complete Orchestration Script output is displayed to the users under the Output column of the ORCHESTRATION tab instead of parsed Output on the Incident, Service Request, and Work Order detail pages. The complete Script output data helps the users to understand what actions are taken by the Orchestration Script. Earlier, a parsed output was only displayed. Parsing is the process of extracting the required chunks of information from the script by executing a set of configured rules. Now, the parsed output is sent as input for the next Script parameter.
Configuration:
Under DETAILS section of the ORCHESTRATION SCRIPTS page (Admin > Advanced > Automation > Orchestration Scripts >Click a Script Name), specify the Keywords and Criteria for the Output Parsing Criteria section.
Criteria | Description |
Remove Before Keyword 1 | Select this to remove the content present before Keyword 1. |
Remove Between Keyword 1 and Keyword 2 | Select this to remove the content present between |
Remove After Keyword 1 | Select this to remove the content present after Keyword 1. |
Remove Keyword 1 | Select this to remove the keyword specified in the Keyword 1 text box. |
Easy error identification with line numbers added to Script Command
Now, line numbers are added to the Script Command in the Script commands text box of the ORCHESTRATION SCRIPTS page (Admin > Advanced > Automation > Orchestration Scripts >Click a Script Name > Under Details section). This makes the Script more readable and helps the users to easily track the failed Script by referring the respective line number.
Example: If the execution of Script fails and output contains line number (example: Error At line: 7), it will help users to identify the exact line where the error occurred.
| Expand | ||
|---|---|---|
| ||
Figure: ORCHESTRATION SCRIPTS Page |
Improved page load performance
When a Orchestration configuration is opened from the list of Orchestration configurations (Admin > Advanced > Automation> Orchestration).
Improved readability of Output by adding Line Numbers
Now, line numbers are added to the Output column of the ORCHESTRATION Tab for Incidents, Service Requests, and Work Orders. This makes the output more readable and helps the users to easily refer the error line while troubleshooting.
| Expand | ||
|---|---|---|
| ||
|
