Customer Fixed Issues and Known Issues Service Automation v7SP1

Owned by Enterprise IT
May 08, 2024

 

What's New | Customer Fixed Issues and Known Issues | Prerequisites | Installation, Configuration, and Upgrade

On this page: Customer Fixed Issues | Known Issues 

Customer Fixed Issues 

Issue NumberIssue DescriptionScenarioResolution
105083

When the PC resolution was set to high (2K resolution) the menus were not getting collapsed.

PC Resolution & settings for which menus were not getting collapsed:

PC Resolution - 1920 * 1080

Scale and Layout Settings- 150%

Browser Name & Version: Chrome (100.0.4896.127)

Steps:

  1. Navigate to Admin > Orchestration > Click Menu.

  2. Click elsewhere on the screen and verify if menus are collapsed.
This issue is fixed and the Menus are collapsed when the PC resolution is increased from 1920*1080.
109536

When the Schedule Type was set to Recurring option, scripts were not getting executed as per the configuration.

Example:

In one of the workflows recurring options was enabled as below.

Retry Interval (In Mins) = 360

Recurring Days = 1 day.

Also, the CPU server utilization was crossing more than 100%.

Steps:

  1. Navigate to Admin > Automation > Orchestration > Orchestration Workflows > Add new Orchestration Workflow.

  2. In the WORKFLOW CONFIGURATION pop-up, Enter Workflow Name, Workflow Category, Description.

  3. On the Workflow Configuration screen, drag and drop the required Scripts.

  4. Navigate to Schedule Type and set it to Recurring.

  5. In Retry Interval and Recurring Days enter the required intervals and days.

This issue is fixed, and the scripts now execute based on the configuration. The CPU utilization crossed more than 100% consumption because of the scripts running every minute, this too has been fixed.

Known Issues 

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

Issue NumberIssue DescriptionScenarioWorkaround
106856After logging out from the Orchestration module by modifying the URL, the user is able to log in to the Orchestration Module without any authentication.

Prerequisite:

  1. The logged-in user should have access to the Orchestration

Bug Reproduction Steps:

  1. Navigate to Orchestration > User > Orchestration.

  2. Click the User profile icon and select the Logout option.

  3. Remove the “#/logout” from the URL.

  4. Browse the renamed URL.

  5. Verify the displayed output.
N/A
106573

Invalid characters are displayed instead of Angular brackets in the tooltip displayed for the Description value on the ITSM Configurations page.

Prerequisites:

  1. The logged-in user should have access to the Orchestration module.

  2. The Description value should be entered within Angular brackets in the Description text area on the ITSM Configurations page.

Bug Reproduction Steps:

  1. Navigate to Orchestration > User >Orchestration.

  2. Click the Menu icon and select the ITSM Configurations

  3. Hover the mouse on the Description column value on the ITSM Configurations page.

  4. Verify the tooltip displayed.


N/A
109724When the user clicks on the Workflow List Sub Menu, the filtered data on the Workflow List page is not cleared, nor is the page reloaded.

Prerequisites: 

  1. The logged-in User should have access to the Orchestration module. 
     
  2. Orchestration Scripts should be configured for a particular category and they should be in Published mode. 
     
  3. Orchestration Workflows should be configured successfully. 

Bug Reproduction Steps: 

  1. Navigate to Orchestration > User > Orchestration. 
     
  2. Navigate to Menu > Workflow Configurations > Workflow List. 
     
  3. Click the Filters icon from the right pane. 
     
  4. Select Workflow Name and enter the workflow name in the search text field. 
     
  5. Click APPLY. 
    The workflow will be filtered based on the Workflow Name mentioned in the Filters. 
     
  6. Navigate to Workflow Configurations > Workflow List
N/A
109806Even if the user has logged out of the Summit Application in another browser tab, the Orchestration tab /page is still accessible.

Prerequisites:  

  1. Service Automation V7SP1 B008 should be deployed successfully. 
     
  2. The logged in User should have access to the Orchestration module. 
     
  3. Orchestration Scripts should be configured for a particular category and they should be in Published mode. 
     
  4. Orchestration Workflows should be configured successfully. 
     

Bug Reproduction Steps:  

  1. Navigate to Orchestration > User > Orchestration. 
    The Orchestration Application will be opened in a New Tab of the browser. 
     
  2. Navigate back to the other browser tab where the Summit Application page is open. 
     
  3. Click the User Profile icon on the Summit Application page.
    Click Log out.
    Summit Application will be logged out successfully.

  4. Navigate to the browser tab where the Orchestration Application page is open and accessible.
N/A
110502Alignment issues with columns and their respective values exist on the Automation Schedulers page. 

Prerequisites: 

  1. Service Automation V7SP1 B008 should be deployed successfully. 
     
  2. The logged-in User should have access to the Orchestration module. 
     
  3. Orchestration Scripts should be configured for a particular category and they should be in Published mode. 
     
  4. Orchestration Workflows should be configured successfully. 
     
  5. Automation Scheduler should be configured with Recurring, Daily, After Every One Minute (Run for 5 Mins), and End Date same as Scheduled Date. 

 

Bug Reproduction Steps: 

  1. Navigate to Orchestration > User > Orchestration. 
     
  2. Navigate to Menu > Automation Schedulers. 
     
  3. Click the Filters icon from the right pane. 
     
  4. Specify an invalid scheduler name in the search text field for the Scheduler Name field. (Invalid Scheduler Name = Scheduler Name which is not in the DB) 
     
  5. Click APPLY. 
    Verify the Scheduler List page which is displayed. 
     
  6. Specify a valid scheduler name in the search text field for the Scheduler Name field. (Valid Scheduler Name = Scheduler Name which is present in the DB) 
     
  7. Click APPLY. 
    Verify the columns and their respective values on the Scheduler List page. 
N/A


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)