Customer Fixed Issues and Known Issues Denali SP3 HF09

On this page: Hotfix Merges | Customer Fixed Issues | Known Issues 

Hotfix Merges

The following Hotfix versions are merged with this release. Please refer to the respective Release Notes for details.

Customer Fixed Issues 

This section describes the issues reported by the customers and their fixes in Denali SP3 HF09 version.

Service Management 

Issue  #Issue DescriptionScenarioResolution
93723In the Incident Management module, the user was able to submit the incident ticket without answering the mandatory feedback question when the Feedback Configuration is enabled.Prerequisites:
  1. Ensure that Feedback Configuration is enabled and a mandatory question is added.
  2. Click Incident > User > My incidents.
  3. Select Tenant and open a resolved ticket.
  4. Click Feedback.
The user cannot submit the feedback without answering the mandatory question.
94296While adding a new reason in the Knowledge Management configuration, spaces were not accepted in the reason name.

Prerequisites:

  1. Click Knowledge > Configuration > Reason and select the Tenant.
  2. Under Actions, click Add New.
  3. In the Reason field, enter a reason with space between the words and click Submit.
Spaces are also accepted in the reason names.
86895

Izenda6 Report e-mail was getting triggered one hour earlier every day, as per configured scheduled time.

This issue was happening for Daylight Saving Time (DST) zones.

Prerequisite:

  1. Navigate to Report.

  2. Click icon to create any new izenda report.

  3. Click on edit icon > MISC > Schedule. Specify the time.

Izenda6 Report e-mail is now not getting triggered one hour earlier every day. It is getting triggered as per the configured scheduled time.

Note: Add the following key in the config file to work with Daylight Saving Time (DST) zones:

 <add key="Izenda:IsDST_forScheduler" value="true" />

90294

While opening an attachment, the following error message was getting displayed:

404: File or directory not found

A few of attachments were getting stored in a different folder without any database name.

Note:  This issue was happening to the customers using SAAS platform.

Prerequisite:

The end user or Analyst attempts to attach a file while raising a ticket.

The attachment is opening without any error message.
93269

On the Configuration Item List page, while opening CMDB, the following error message was getting displayed for the end-user.

Oops! An error occurred.” 

Note: This issue was happening when the User Access Configuration was enabled. (CMDB > Configuration > User Access Configuration).

Prerequisite:

Navigate to CMDB > User > Configuration Item List. The Configuration Item List page is displayed.

On the Configuration Item List page, the end-user is able to open CMDB without any error message.
94334

If the SR got Rejected analyst was unable to search from Analyst search using complete id (with SR prefix)

For example, in the SR SR500018 if prefix ‘SR’ was removed and searched only with 500018 then it was showing the record.

Prerequisites:

1)As an analyst searched for any Rejected SR in global search by specifying SR3456> Results are not displayed.

2)As an analyst searched for any Rejected SR in global search by specifying 3456>Results are displayed.

Rejected SR can be searched by analyst in global search along with the ‘SR’ prefix too.

94325


Orchestration Script was not getting attached to the work order when the previous work order was resolved by the API Call.

But the same script was getting attached to the work order when the previous work order was resolved manually or resolved through the “Auto Update” feature present in the Step 3 – Auto Update tab of the Orchestration.

NAOrchestration Script is getting attached to the work order when the previous work order was resolved by the API Call.
93525

Push report was not sending the scheduled report in Server Utilization report for Graphical type. If rescheduled an oops error was displayed.

Push report was working only for Tabular type.

Prerequisites:

1)Reports > Server Utilization Report.

2)Select Report View >Graphical type.

3)In Push report add Date, Time to trigger

Fusion charts mismatch is fixed which caused the error.

Push report sends the report for Graphical type successfully without any errors.

Asset Management 

Issue  #Issue DescriptionScenarioResolution
92439

The user was able to accept an asset without conforming to the terms and conditions even though the configuration for ‘Accepting Terms and Conditions’ was enabled for the end user.

Preconditions:

  1. Asset Usage Type should not be configured or must be inactive for the tenant.
  2. At least one asset must be available in the ‘Pending Acceptance’ state that is allocated to the user.
  3. The tenant level configuration ‘Enable Terms and Conditions in Asset Acceptance’ should be enabled for the Asset category in which the above asset belongs to. Also, terms and conditions should be configured for the selected asset category in Asset Allocation Template Configuration

Steps:

  1. Navigate to Dashboard > User Dashboard > My Assets.
  2. Select an asset in the ‘Pending Acceptance’ state for which above configurations are applicable.
  3. Click ACCEPT icon on the Actions panel and then ACCEPT button on the ACCEPT ASSET pop-up.
  4. Verify whether the validation message is displayed or not.
After the resolution, the user is not able to accept an asset without conforming to the terms and conditions specified for the same. If the user attempts to accept an asset without agreeing to terms and conditions, a validation message is displayed, and the acceptance is not done.
93637

Some details of the aged Assets were not displayed in the ASSET AGEING BY CUSTOMER REPORT.


Asset Ageing Report lists the customer-wise asset counts with time frame that are out of their warranty period. Once you click the asset count, the category-wise asset ageing details need to be displayed in a table. But the table did not display some of the asset values such as Serial Number, Make, Model data, etc.

Steps:

  1. Navigate to Report > Asset Management > Asset Ageing By Customer Report.
  2. Select
  3. Click on the count drilldown.


The Ageing Report displays all the concerned data of the aged assets correctly in the table.

IT Operations Management

Issue  #Issue DescriptionScenarioResolution
92432

For non-Wintel servers, data about the CD ROM Drive was getting captured during the Hard Disk monitoring and the customer was getting alerts when any actions happen on that CD ROM Drive.

Prerequisites:

  1. Click Operations > User > Views > Server View.
  2. Click Filters and select the Tenant and the required filters. Click Submit.
  3. Click on any non-Wintel server and click on HARD DISK.

All hard drives data will be seen in the HARD DISK page.

Hard disk monitoring is configured using a command in the backend and the CD ROM monitoring must be excluded with the command.
92611

When adding the discovered devices to the existing network topology in the Network View, there was a timeout error, and the discovered devices were not displayed in the available list. Hence, the user was not able to add new devices from the discovery.

The time out was happening because the view state data was checking by a security option which was enabled in nginx. It was taking time to get the response from the application server and the timeout was happening.

Prerequisites:

  1. Click Operations > Configuration > Networks > View > Edit View.
  2. Click on any view name from the list.
  3. Click ADD DEVICE and select the discovery job from the Job Name dropdown list.

The devices were not displayed under the Available Devices.

The discovered devices are displayed under the Available Devices.
93459In the CMDB, the CI location was not getting mapped for the network devices from the ITOM module.

Prerequisites:

  1. Click Operations > Configuration > Servers > Server List. Click Filters and select the Tenant.
  2. Click ADD NEW > Advanced. Select a location from the Location dropdown list and fill the required details and click SUBMIT.
  3. Click CMDB > User > Configuration Item List.
  4. Click on the CI item that is created in step 2.
  5. Click on General tab and check the Location value. Location provided in step 2 and the location value here in the CMDB CI information should be same.
Note: The CI location can also be verified for the Network device and the Network link in the same way.
The CI location is getting mapped correctly from the ITOM module.

Change Management

Issue  #Issue DescriptionScenarioResolution
93109

An approver unable to approve an emergency Change Record due to selected schedule date and time.

A validation message ‘Planned End Time is less than Log time’ when the user specified the date and time less than to the log date and time.

The approval could approve an emergency change record even if the planned start and end time is less than Log time.

Orchestration

Issue #Issue DescriptionScenarioResolution

95428

When the password was specified against a Script parameter with Data Source as Password in Step 2 - Configure Actions tab of Orchestration page, the password was not getting encrypted in the backend. Instead, the password was saving as a plain text.

Prerequisites:

  1. Click Admin > Advanced > Automation > Orchestration.
  2. In the ORCHESTRATION page, click on any one of the orchestrations listed or add new Orchestration.
  3. Click Step 2 - Configure Actions tab and perform one of the following steps:
    1. Click on the Edit symbol for one of the actions listed in the table at the end of the page.
    2. Fill the details and select a script in the Script Name dropdown list.
  4. One or more parameters will be displayed for the selected script. For one of the parameters, select Password from the Data Source dropdown list, enter the password value in the Data Field, and click Submit.

The new saved password must be saved in an encrypted format but it is saving as plain text.

When the password was specified against a Script parameter with Data Source as Password in Step 2 - Configure Actions tab of Orchestration page, the password is now getting encrypted in the backend. Encrypted password now provides more security than earlier password saved as plain text.


Known Issues 

This section describes the known issues detected by the SummitAI Dev and QA team in the release, Denali SP3 HF09.

Issue NoIssue DescriptionScenarioWorkaround <if applicable>
88818

The value selected for the Priority is getting cleared after CAB Approval.

Prerequisite:

Configure a PIR Reviewer.

Bug Reproduction Steps:

Click Change > User > New Change Record.

Create a CR by selecting the Change Type as Emergency and e-CAB Approval Required as After Implementation.

Authorize the CR.

Implement the CR.

Approve the CR.

This issue occurs only when the CAB approver approves the CR.

NA
Issue

While trying to uninstall the TLS 1.2 agent from the control panel, a pop-up message “Network connect failed. Please contact Administrator “is displayed and TLS 1.2 agent was not getting uninstalled.

Work around: Using the Uninstall_SAM_SSI.exe, you can uninstall TLS 1.2 agent. (#87625)

Under the Asset Movement Details section of the Asset Transaction Details Report, the assets which are in In-Transit status and waiting for movement approval (such as Return From Repair movement approval, Send To Repair movement approval, and Assets waiting for Deactivation approval) are not getting displayed. (#86416)

Under the Checker Status column of the FIXED ASSET inventory page, When the Fixed Asset is allocated the Asset status is shown as Referred Back even though the Maker-Checker configuration is disable for the Allocate asset transaction. This issue occurred when the Maker-Checker configuration is enabled for the Deallocate and Deactivate Asset transactions and the Checker refers back the asset deactivation request.

In an ideal scenario, the Checker Status column of the FIXED ASSET inventory page must get cleared after allocating the In-Store asset that was referred back by the Checker for asset deactivation request. (#83900)

Mail Parser configured with O365 API cannot run on the summit Proxy Server, it can only run on the Summit Server. Email to ticket creation feature is not supported for the following configuration combination on the MAILBOX page.

 Server Type = O365 API

 Monitoring Source = Proxy Server 

Note: Email to ticket creation works when you select Server Type as O365 API and Monitoring Source as Summit Server.

The MAILBOX configuration page can be accessed using Admin > Advanced > Notifications > Mailbox. (#83831)

When the user re-login into the SummitAI application and performs the same action for the second time on the same page (Ex: MY APPOINTMENTS) and clicks SUBMIT, an error message “Error Occurred” is displayed. 

This issue is found when the user has logged into the SummitAI application using the Microsoft Internet Explorer browser (IE Version: 11.719.18362.0) (#82553).

Issue 1: Urgency and Impact values of Orchestration are not getting updated on the SR details page. Orchestration values should override the Catch & Dispatch values.

Pre-Requisites: 

In Catch & Dispatch configuration page, switch to Service Request Module and select Show As Recommendation checkbox for all.

In the Orchestration Configuration page, select Update if any one action fails in the On Failure drop-down list and keep the Do not update if value already exists checkbox unchecked.

Bug Reproduction Steps:

Navigate to Request > New Service Request.

Create an SR where Orchestration script is linked.

Navigate to Request > Service Request List page.

Access the same Service Request and apply the catch and dispatch value from CINDE Suggestion popup.

After Orchestration script fails, all Service Request details should update as per the Orchestration configuration.

Verify the Service Request details against Orchestration configuration values.


Issue 2: Similar issue was also found for the prerequisite of On Success criteria configuration being Resolve if all actions are successful. This paired with Do not update if value already exists check box not being selected led to a similar bug. (#83602)
SAM Agent unable to block the installed software’s, mapped in the Master profile though the same software is getting block when mapped with the normal profile of an Asset. The master profile should work as default when a normal profile is configured for the Asset. (#82494)

In the Universal Agent, Software installation is not working through Run Book Automation (RBA) script. (#83612)

After configuring the remediation Script as User-preference in the new Universal Agent, the Endpoint Automation (EPA) is not working and the EPA script is always displayed with In-progress status. (#83611)

Post the SAM agent update, the Software Silent Installation functionality using RBA script is not working. This issue is occurred when the Agent machine has two IP addresses (#83770)

The servers with IP Addresses 192.168.100.30, 192.168.100.100 servers, the Universal Agent parameter EPA, Patch Management, and RBA functionalities were not working. The application was showing the following error message (#82939):

Error Message: The underlying connection was closed: An unexpected error occurred on a send.

   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)

   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)

   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

   at SAMAgent.Entwidgets.Service.GetRBAScripts(String sAssetInfo, String sProxyName, ProxyDetails _pxy)

   at SAMAgent.AssetDetails.Agent_RunbookAutomation.ExecuteRBA()

   at SAMAgent.Program.Main(String[] args)

 

When an AD Import record is modified on IE Version 11.719.18362.0, the error message is displayed as “Error Occurred” when you click SUBMIT button on the AD IMPORT page (Admin > Basic > Users > Import > AD Import(#82733).

While raising a CR, if the Requestor is changed after selecting Category and Change Type, the Line Manager and Reporting Manager for the selected Requestor are not getting updated in the workflow.

But after submitting the CR, the Line Manager and Reporting Manager are updated in the workflow based on the selected Requestor.

Similarly, the same issue is happing while raising CR using a template too.

While importing data through the Import Excel option, the Include Sub-Customer value in the respective column can only be True or False for all the statuses in the excel sheet.

To import the excel navigate to:

SR: Request > Configuration > Others > SMS Notification > Select the Tenant > Select the IMPORT option under ACTIONS panel.

IM: Incident > Configuration > Others > SMS Notification > Select the Tenant > Select the IMPORT option under ACTIONS panel.

(#81164)

On the Incident Details/ Service Request Details page (Incident/ Request > User > Manage Incidents/Manage Service Requests > Incident List/Service Request List > Click an Incident ID/SR ID), click the Assigned To drop-down where analysts are displaying, but their availability status is not displayed (#78647).

Application is allowing the Administrators to save the Connector details though there is a validation message while updating the Connector details page. The Connector details page can be accessed from EDIT VIEW page (Operations > Configuration > Networks > View > Edit View > Select the required device from the list > Click the Connector on the Drawing Board > Click Edit Node to update the Connector details > Update the details with incorrect data to pop-up the validation message > Click SAVE).

(#81100)

After adding a new device on the Drawing Board of the EDIT VIEW page sometimes the position of the added device is not displaying correctly on the Drawing Board. The Edit VIEW page can be accessed using (Operations > Configuration > Networks > View > Edit View > Select the Tenant and other required details> Click Add Node icon and click on the empty space of the drawing board to add devices into the View > Click SUBMIT).

(#80641)

The following issues are there on the EDIT VIEW page (Operations > Configuration > Networks > View > Edit View > Click ADD NEW on the ACTIONS panel > On the DRAW VIEW page, select the Tenant and other required details > Click ADD DEVICE on the ACTIONS panel to add devices into the View > On the ADD DEVICE pop-up page, select the devices you want to add to the View and click SUBMIT) while adding a new device to the view:

The existing devices on the page are not getting displayed.

The validation message is not populating while submitting without selecting the devices.

(#80269)

When the Maker-Checker configuration is enabled for the Allocate action and Maker-Checker approval matrix is configured with two levels of approval, on sending the Allocated Assets for Checker’s approval, the following issues are observed:

On the FIXED ASSET page (Asset > User > Manage Asset > Asset Inventory > Click the FIXED icon under the SELECT THE ASSET TYPE section > Click FILTERS on the ACTIONS panel > Select Status as Allocated and provide data in all the other fields > click SUBMIT), duplicate Assets are displayed after the Checker approves the Assets sent for approval.

The Assets do not move to the second level of approval after the Assets are approved by the first level of Approver.

Prerequisites

Enable Maker-checker approval for Asset Allocate transaction. (AdminBasic > Infrastructure > Tenant > Click Filters on the ACTION panel and select the Domain and click SUMBIT > On the TENANT page under the LIST section, select the Tenant for which you want to enable Maker Checker > Click CONFIGURE DETAILS on the ACTIONS panel > Click Asset Management under the MODULES section > select the check box of Enable Maker-Checker > Select Actions for Maker-Checker to Approve as  Allocate > Select the End Time value and click SUBMIT).

Configure No. of Approval level as 2 on the APPROVAL MATRIX page (AssetConfiguration > Others > Approval Matrix > On the ACTIONS panel, click ADD NEW > Specify the details > click SUBMIT).

Send Assets for approval for Allocate action (Asset > User > Manage Asset > Asset Inventory > On the ASSET INVENTORY page, under the SELECT THE ASSET TYPE section, click FIXED > Select the same Tenant for which the Maker-checker is enabled >  Click the In-Store hyperlink of the required Asset Category > Select the check box corresponding to the Asset you want to allocate > On the ACTIONS panel, click ALLOCATE > Specify the mandatory details to allocate the Asset and click SUBMIT).

Bug Reproduction Steps:

Login to the Application as Checker.

Click Asset > User > Manage Asset > Approvals Maker-checker Approval > Click Filters on the ACTIONS panel.

On the Filter pop-up page, select the Tenant and specify the required details.

Select the Assets that you want to approve and click APPROVE icon on the ACTIONS The APPROVE pop-up page is displayed.

On the APPROVE pop-up page, select the Approval Status as Approved to approve the Asset and click

Click Asset > User > Manage Asset > Asset Inventory > Click FIXED under the SELECT THE ASSET TYPE section > Click Filters on the ACTIONS

On the Filters pop-up page, select the Tenant, Select the Status as Allocated and specify required details.

Click SUBMIT.

Validate the data.

(#72171)

The GetBulletinBoard Mobile API request is used to retrieve Bulletin Board information. The User ID and Tenant Code are passed as the Request Parameters. In the API Response, instead of displaying the Bulletin Board information for the specific User ID and Tenant, the Bulletin Board information for all the Tenants is displayed. (#73031)

Prerequisites:

Configure Bulletin Boards for multiple Tenants.

Bug Reproduction Steps:

Log into the Application as an Administrator.

Configure a Bulletin Board. For more information, see Configuring Bulletins.

Send a POST request for the GetBulletinBoard API. Pass Tenant Code, in the Instance parameter and User ID in the UserID parameter.

Check API Response, instead of displaying the Bulletin Board information for the specific User ID and Tenant, the Bulletin Board information for all the Tenants is getting displayed.

On the ACTION DETAILS pop-up page, the Target ID is not showing in the Target column when Status of the Orchestration Workflow Script (other than the first Script) is In-Progress, and it is having Target Host Type mapped to From Previous Output valueHowever, the Target ID is displayed after the Script is executed successfully. (#73079)

Note: This issue is found in Incident Management, Work Order, and Service Request Management (SR) modules. Following bug reproduction steps are for the SR module:

Bug Reproduction Steps:

Log into the Application as an Administrator.

Select Admin > Advanced > Automation > Orchestration.

On the WORKFLOW LIST page, click the NEW

On the WORKFLOW CONFIGURATION pop-up page, select Module as Service Request, and specify other details to configure the Orchestration Workflow.

Map the Target Host Type to From Previous Output value for the scripts of the Orchestration Workflow.

Log out and log into the Application as an Administrator or as an Analyst.

Select Request > Manage Service Requests > Service Request List.

On the SERVICE REQUEST LIST page, specify the Filters and open an SR.

On the SERVICE REQUEST DETAILS page, click the ORCHESTRATION tab.

On the ORCHESTRATION tab, click the Script When the Script (other than the first Script) is in In Progress status, check the Target column details on the ACTION DETAILS pop-up page. The Target ID is not displaying in the Target column.

After successful execution of the Script (other than the first Script), click the Script hyperlink. Check the Target column details on the ACTION DETAILS pop-up page. Now, the Target ID is displaying in the Target column.

The previous Asset transaction details are not displayed under the Previous Transaction drop-down list on the PREVIOUS IMPORT DETAILS page (Asset > User > Manage Assets > Import > Import Asset > Specify all the details > Click SUBMIT), even though the Assets are approved by the Checker on the MAKER-CHECKER ASSET-APPROVAL page (Asset > User > Manage Assets > Approvals > Maker Checker Approval > Click Filters  on the ACTIONS panel > Specify the filter criteria to view the list of requests from the Maker > Select the Assets that you want to approve under the LIST section > Click APPROVE on the ACTIONS panel > Select the  Approval Status as Approved.) This issue is found when the Asset Maker Checker Configurations is enabled.

(#67240)

When a user opens any page in a new tab in the SaaS Environment, the Switch Tenant pop-up is displayed in all the pages. This issue occurs only when the user is using the Firefox private window/tab. (#72276)

On the ADMIN DETAILS page (Admin > Advanced > Password Management > Administrator > Click ADD NEW on the ACTIONS panel > Specify all the details > Click SUBMIT > Select the Domain Name on the LIST page), the Password field is not displaying the GUID or Encrypted ID of the password and the field is empty. This issue is found when the user is logging into the SummitAI application using Microsoft Internet Explorer browser.

On the Incident Management FORM BUILDER page (Admin > FORM BUILDER > Select a Tenant > Select Module as Incident Management > Click Add on Actions panel> Select Display At as Additional Information or General Area or TFS Area > Click Next), when a user configures single Parent and multiple Child using Common Master, the collective values of both Child 1 and Child 2 are displayed in Child 1 and Child 2 drop-down lists.

On the Service Request Management FORM BUILDER page (Admin > FORM BUILDER > Select a Tenant > Select Module as Service Request > Click Add on Actions panel> Select Display At as Additional Information or General Area or TFS Area > Click Next), when a user configures single Parent and Multiple Child using Common Master, the collective values of both Child 1 and Child 2 are displayed in Child 1 and Child 2 drop-down lists.

The configured Bulletin Board (Admin > Advanced > Notifications > Bulletin Board > Select the Tenant > Click ADD NEW to configure the Bulletin details > Click SUBMIT) is displayed on the END USER DASHBOARD page even if the user does not have access to the selected Tenant and Domain.

Overlapping of content is observed on the Pagination bar of all the pages having high amount of data (typically in the range of 5 digits).

Broken image of the logo is displayed in the application when the logo image is deleted from the APPLICATION SETTINGS page (Admin > Basic > Infrastructure > Application Settings).

Workaround: The users need to re-login to the SummitAI application after deleting the logo.

On the AUTO-RESOLUTION SERVICE REQUEST CONFIGURATION and AUTO-RESOLUTION INCIDENT CONFIGURATION page (Admin > Basic > Infrastructure > Tenant > Select Domain > Select Tenant which is configured with Service Request/ Incident Management module > Click CONFIGURE DETAILS on the ACTIONS panel > Under the For End Users tab, select a reason form the Enable Reminder to Callers for Pending Reasons drop-down list > Enable Auto-Resolve Service Requests/ Auto-Resolve Incidents check box > Click Set Fields for Auto-Resolving Service Requests/ Set Fields for Auto-Resolving Incidents link), the users can set the auto-resolution criteria by specifying only white space (not numbers and alphabets) in the Response SLA ReasonResolution SLA Reason, and Solution fields.

The following issues are observed in BI Custom Reports:

When a user downloads the report (in any format), the data is displayed with hyperlinks.

When a user places the mouse cursor on the count link, the tooltip is displayed as [Object Object].

In the exported report, report name is displayed with '+' instead of space.

The Change Record is not created when the CR Requester and Customer Approver are same. This issue occurs even though Do Not allow Customer Approval of CR check box is selected on the Change Management TENANT configuration page. This issue occurs only for the first time when the Tenant is configured.

Workaround: The Administrator needs to unselect and again select the Do Not allow Customer Approval of CR on the Change Management TENANT configuration page (Admin > Basic > Infrastructure > Tenant > Select the respective Tenant for which this issue is occurring > Click CONFIGURE DETAILS on the ACTIONS panel > Enable Do Not allow Customer Approval of CR check box and click SUBMIT > Clear Do Not allow Customer Approval of CR check box and then click SUBMIT, again).

The new SLA Value of an Incident is not displayed on the CHANGE HISTORY pop-up page (Incident > User > Manage Incidents > Incident List > Select the required Incident ID from the list Click CHANGE HISTORY on the ACTIONS to view the change history of the selected Incident) when an incident is moved from New status to In-Progress using Notification Services.

The Pending Reason of an incident is still displayed on the CHANGE HISTORY pop-up page (Incident > User > Manage Incidents > Incident List > Select the required Incident ID from the list Click CHANGE HISTORY on the ACTIONS to view the change history of the selected Incident), when an Orchestration Script fails and the respective Incident is moved back from Pending to In-Progress.

The notification e-mails related to escalation and jobs are triggered only in English language irrespective of the configured language on the NOTIFICATION TEMPLATE page for all the modules (AdminAdvancedNotificationNotification Template> Select a Tenant > Click ADD NEW > Specify all the required fields > Click SUBMIT).