Customer Fixed and Known Issues

Steps:

1.Navigate to Admin > Automation > Orchestration.

2.In the Orchestration application, Navigate to Workflow Configuration > Workflow List.

3.Click Action for a selected Workflow.

4.Verify the count of Success and Failure of a Workflow in reference to Ticket ID/ Ref ID in Execution History that is displayed in the bottom panel.

1. Navigate to Admin > Automation > Orchestration.

2.In the Orchestration application, Navigate to Workflow Configuration > Workflow List.

3.Select any Workflow from the list.

4.In Workflow Configuration, click any script, Script Details is displayed on the right panel.

5.Navigate to Schedule Type select Recurring. Specify Retry Interval as 5 minutes (specify 10 minutes or 15 minutes as needed).

6.Enter Recurring Days as required.

7.Verify if scripts are running for time mentioned in Retry Interval.

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.

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.

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.

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. 

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)

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.

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".

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)