Download Release Notes | Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali SP1 << Denali SP1 HF01
On this page: Customer Fixed Issues | Known Issues
Scroll export button | ||||||||
---|---|---|---|---|---|---|---|---|
|
AnchorCustomer Fixed Issues Customer Fixed Issues
Customer Fixed Issues
Customer Fixed Issues | |
Customer Fixed Issues |
This section describes the issues reported by the customers and their fixes in Denali SP1 HF02. The bug fixes for the bugs found in the following version are also merged with this release. Please refer to the respective Release Notes for details.
# | Issue | Resolution |
---|---|---|
75895
| Prerequisites: 1.Configure the Orchestration Script with input parameters. The configured Script parameters were not displaying under the Step 2 - Configure Actions tab of the ORCHESTRATION page. This issue was occurring when an Administrator tried to edit the configured Script. Bug Reproduction Steps:
| Now, the configured Script parameters are displayed under the Step 2 - Configure Actions tab of the ORCHESTRATION page even when an Administrator tried to edit the Script. |
77562 | The Child Work Order that was configured with the Conditional Creation was not getting created under the RELATIONSHIP tab of a logged SR. This issue was occurring only when the Parent Work Order of a Catalog was resolved on execution of the Orchestration Scripts. Bug Reproduction Steps:
| Now, the Child Work Order is created after the resolved Parent Work Order by the Orchestration and displayed under the RELATIONSHIP tab of a logged SR. |
77285 | The following issues were occurring while logging an SR through the API key login method:
| Now, the ENTITLED SERVICE icon is not appearing on the DETAILS section pane and the E-mail notification is triggering to the Caller. |
76691 | The auto-escalation e-mail for Service Request Response SLA violation was getting triggered to the user of a different Tenant instead of the user configured for the same tenant. | Now, auto-escalation e-mail for Service Request Response SLA violation e-mail is triggering to the user of the same Tenant. |
77293 | On the EXPORT CONFIGURATION BY FILE page, the Category and Classification options were not displaying for the Incident Management module even after selecting these options under the Master Types. | Now, the Category and Classification options are displayed on the EXPORT CONFIGURATION BY FILE page. |
76103 | The following GET method was invoking after the session timeout and displaying an invalid access. Sample error: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. SummitNet.WS.Common.GeneralConfigService..ctor GET-/ws/common/generalconfigservice.asmx/refereshsessiontimeoutcookies System.Exception: Invalid access! ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. at SummitNet.WS.Common.GeneralConfigService..ctor | Now, it is not invoking the refereshsessiontimeoutcookies method after the session timeout. |
The following error was displaying while the session was not initialized. This error message was captured and suppressed in the code. Sample error: System.NullReferenceException: Object reference not set to an instance of an object. SummitWeb.BasePage.get_LicenseEdition GET-/summit_ssologin.aspx Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. | Now, it is fixed by handling the Null condition. | |
The following error was occurring due to the Time Zone check. Sample error: System.TimeZoneNotFoundException: The time zone ID '(UTC - 05:00) EST - Eastern Standard Time' was not found on the local computer. System.TimeZoneInfo.FindSystemTimeZoneById POST-/summit_samlresponse.aspx The time zone ID '(UTC - 04:00) EDT - Eastern Daylight Time' was not found on the local computer. | Now, the code is removed since it is not in use. | |
The following error was occurring due to an old HTML tag for DScript that contained only DIV tag. Sample error: Unexpected character encountered while parsing value: <. Path '', line 0, position 0. Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path '', line 0, position 0. at Newtonsoft.Json.JsonTextReader.ParseValue | Now, the HTML tag is handled to support the JSON conversion. | |
The following error was displaying while the session was not initialized. This error message was captured and suppressed in the code. Sample error: System.NullReferenceException: Object reference not set to an instance of an object. at LayoutMaster.master_Page_PreLoad at System.Web.UI.Page.OnPreLoad | Now, it is fixed by handling the Null condition. |
Fixed API Issues
This section describes the API issues fixes in the release, Sierra SP1 HF09.
Fixed API Issues |
---|
The following issues are fixed for the IM_LogOrUpdateIncident API:
|
AnchorKnown Issues Known Issues
Known Issues
Known Issues | |
Known Issues |
This section describes the known issues detected by the SummitAI Dev and QA team in the release, Denali SP1 HF02.
Issue |
---|
On the SEARCH ASSET page (ASSET > USER > MANAGE ASSETS > ASSET INVENTORY page > Click Non-Fixed Asset icon (Consumable, Accessories, or Software) > Click Search Asset icon), an error message "Oops! An error occurred" was displayed when the length of the specified search text is more than 30 characters. This issue exists for the following scenarios:
(#73532) |
For the Custom Attribute (Drop-down), if any value is set as default on the Form Builder page (Admin > Basic > Infrastructure > 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 > Drag and drop the Drop-down Custom Attribute > Type in the Label for the Custom Attribute > Select Options (data source) as Manual > Type in the Drop-down Values and Make one value as default), then the default value is not automatically set for that Custom Attribute (Drop-down) across the Incident Management module (#71703). |
If the SLA is paused during the PR resolution and the Paused Time is before RCA Deadline, the paused duration is not getting added to the Resolution Deadline. This issue is occurring when the Resolution Deadline Type is selected as RCA Deadline Time in the Deadline Configuration. (Bug#74495) Note: If the SLA Paused Time is between RCA Actual Time and RCA Deadline, the paused duration does not consider for the Resolution Deadline. Example: Consider the PR Log Time as 9:00 AM, RCA Deadline as one hour, and Resolution Deadline two hours. The paused duration does not add if the Analyst performs the below actions:
The Expected Resolution Deadline should be: RCA Deadline Time + Resolution Deadline + Paused Time = 10:00 AM + 2 hours + 10 mins = 12:10 PM. |
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:
Prerequisites
Bug Reproduction Steps:
|
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:
|
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 value. However, 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:
|
On the IMPORT ASSET and ADD ASSET pages, the users can add multiple Assets with same Serial No., although, Serial No. is a unique field for Assets. This issue is found if Maker/Checker configuration is enabled. For example, a user added an Asset with Serial No. 123 and is pending for Checker’s approval. The user is able to add another Asset with same Serial No. 123. And send for Checker’s approval. The Checker is also able to approve two Assets with same Serial Number on the MAKER-CHECKER ASSET-APPROVAL page. Bug Reproduction Steps:
(Bug#67236) |
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 Reason, Resolution SLA Reason, and Solution fields. |
The following issues are observed in BI Custom Reports:
|
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 (Admin> Advanced> Notification> Notification Template> Select a Tenant > Click ADD NEW > Specify all the required fields > Click SUBMIT). |
Scroll ignore | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|