Known Issues

This section describes the known issues detected by the SummitAI Dev and QA team in the release, Service Automation.

Issue
Administrator uninstalls a proxy. Log in to the application as an administrator. Uninstalled proxy is still listed in the Proxy Configurations page (Admin > Advanced > Automation > Orchestration > Proxy Configurations > and Status displays as Up. (#85111)
Click on the icon on the Script Configurations page (Admin > Advanced > Orchestration > Script Configurations). Search for the values which are not available in the grid. System displays other existing record entries instead of displaying the message “No Data”. This is the issue with all columns such as Script Name, Status, Category, Script Language, Created By, Created Date, Last Updated By, Last Updated Date, and Description on Script Configurations page. (#84577)
When the Live Feed button is disabled, Live Feed window does not display the tickets which are not live anymore and have executed previously. (#85499)
The following is the issue with the exported excel of all the list pages with Export to Excel option: Column names are not displayed in the same order as on main List (#85113)
Having configured an orchestration workflow with no connection from Failure to End, once the workflow moves to Failure state in the ticket, and analyst clicks on the View, on the Workflow Viewer, there is no connection displayed from Failure to End. (#86093)
Log in to the application as an Administrator. Go to Orchestration Workflows > Period. It does not display the current time along with selected date for the fields From and To. (#85795)
Log in to the application as Administrator. Go to Orchestration Workflows > Period. Today’s date is not highlighted in the calendar for the fields From and To. (#85796)
When the admin clicks on the 'if condition object' at Variable Name field, even the 2nd script's output variables are displayed. This issue is observed when you have placed an 'if condition object between 1st and 2nd orchestration script and the if condition is connected to the 2nd orchestration script'. (#85131)
When multiple CIs are linked while creating the SR then Service Automation execution is not working correctly. Pre-requisites: 1. Catalog should be configured with CI. 2. SR Should be created for the above catalog. Steps to reproduce the issue: Log in to SUMMIT application and navigate to New Service Request. Select the Service Catalog for which Orchestration is configured. Link at least 2 CI in the Catalog form. Click Submit to create a New Service Request. Log in to SUMMIT application as an analyst. Navigate to Request > Service Request List. Select the above created Service Request. Click Orchestration Tab. Scripts are executed multiple times for the same CI. (#85376)
The script execution fails when “Remote Execution By" is set as "CI Account" on the script configuration page and "Target Host" is selected as the Orchestration Proxy server on the Orchestration Workflows page. Pre-requisites: Configure a script with "Remote Execution By" set as “CI Account” under the Execution Tab. Select the configured script to 'Workflow designer'. Select 'Target Host' as orchestration proxy. Raise and validate an SR (#85494)
Under the Action dropdown of the second script all the script variables are displayed. For example, script 3 variables are also displayed in action dropdown of the second script. Pre-requisites: 1. This issue occurs when you have configured 3 scripts on the designer page. 2. You have linked the first script to the second script and have configured the second script Target host type as "From previous output". (#85769)
At Proxy IP Mapping page, upon entering a single digit at From IP/To IP fields and even before completion of entering the complete IP Address, a validation message is displayed. Pre-requisites: Orchestration Angular Build has to be deployed Orchestration API has to be hosted Summit API has to be hosted Orchestration Proxy has to be installed Steps to reproduce: Login to the application as an admin. Go to Admin > Advanced > Automation > Orchestration. Go to Proxy Configurations page. Under Host Name column, click on the host name of the proxy machine > Proxy IP Mapping page will open. Under IP Range section, at From IP/To IP fields, just enter any 1 digit number (Example: 1) (#83636)
The Session expiry message is not displayed to the Admin even after the session has expired on the Orchestration pages. Pre-requisites: The Orchestration environment should be configured. Steps to reproduce: Login to SUMMIT application. Navigate to Admin > Automation > Orchestration. User should not close Orchestration window and not perform any action or it has to be idle for a long period. Session timeout alert is not displayed to the User. (#84075)