Work Order notifications displayed inconsistent behavior, with the Symptom and Description details being populated in some cases and blank in others.
Work Order notifications consistently display the Symptom and Description details.
183597/183593
Approval notification was sent to all the approvers configured as part of the workflow, Even if as per conditions configured in workflow, an approver was not supposed to get email, as conditions were not matching, still the approver was getting email notifications.
Based on the applicable conditions met, only relevant approvers based on matching conditions are getting approval notification emails.
183961
The data was not getting filtered accurately, on Manage Service Request page, when the Operator under the Advanced Filter was selected as After, On or After.
The data is getting filtered accurately, on Manage Service Request page, when the Operator under the Advanced Filter is selected as After, On or After.
183417
When a column-level filter was applied and the user clicked on new without clearing the filter, the same filter was carried over to the Import Template pop-up.
The issue where column-level filters were carried over to the Import Template pop-up has been resolved.
159895
Whenever a file was attached, error “Something went wrong”appeared. File had XMLdata,and it was a txt file.
No error message on file attachments.
100929
The column-level filter remained active and carried over into the Import Template popup when the user clicked New without clearing it.
This has been implemented to prevent column‑level filters from carrying over into the Import Template popup.
184044
The Reporting Manager Role Based Approvals were not populating.
Scenario:
For two catalogs Reporting Manager approval was not populating:
Azure or M365 Administrator Role Form
Display Name / Email Address Change Request
In the workflow, the Reporting Manager was not working as expected with the configured with dot-walking (Requestor.Manager).
The Reporting Manager Role Based Approvals is populating as expected.
Known Issues
Issue ID
Issue Description
Scenario
Resolution
84144
Users are not able to create the duplicate Priority Matrix.
Steps:
Login to the application as an Application Designer.
Select Service Management application.
Click on settings icon and select the Module as Problem.
Navigate to Configuration > Priority Matrix.
Select already existing field value for the Impact, Urgency, Priority fields.
Verify the Priority Matrix configuration.
NA
79411
User is not able to save the Target Form created through Form Relation when multiple files are attached in the Source Form.
Steps:
Login to the application as an Analyst.
Navigate to Service Management > Incidents > Manage Incidents.
Click New button on the list page.
Fill all the mandatory details.
Upload the file in Attachment field.
Click on Save button.
Access the same created by clicking on ID hyperlink.
Navigate to Links tab and click on Create button and select the module for which form relation is configured (Example: INC to SR.)
Verify the uploaded file in Attachment field.
Click Save button and verify whether user can save the Target Form (SR).
Verify the toast message.
NA
79372
Users are experiencing alignment issue in the Create tab of Links tab in the Form Designer.
Steps:
Log in to the application as an Application Designer.
Navigate to Service Management > Design Studio > Select Module as Incident > Form Designer.
Select Manage Incidents form and place the form in Maintenance.
Navigate to Design Form step.
Click on the gear icon of Links tab.
Click on Create tab and verify the alignment of add icon '+'.
NA
171982
The Problem Record status is not reflected on the linked Incident or Service Request, and the Parent-Child option is missing in the Link popup.
Steps:
Log in to Apex application.
Select Service Management application.
Navigate Problem > Manage ProblemRecord. The Manage Problem Record List page is displayed.
Click existing PR ID and navigate to Links tab.
Select Incident or SR. The Link pop-up appears.
In the pop-up, select the Parent-Child relationship from the dropdown.
NA
79887
The Define Conditions step in the Notification Parser displays UI alignment inconsistencies and text translation issues after configuring line forms and define keys.
Steps:
Log in to the Apex application.
Navigate to Settings > Design Studio > Application > Notification Parser. The Notification Parser List is displayed.
Click New and fill in all mandatory fields.
Navigate to the Parser Content step. Fill in all required Line Form entries.
To add or update form data, select the relevant line form and configure the Define Keys.
Select Define Conditions step.
N/A
78560
Only one email was converted into a ticket. The remaining emails were not processed or converted.
Prerequisites:
API Configuration is set up
Mailbox is configured correctly
Notification Parser is configured
Steps:
Log in to the application as an Admin.
Navigate to Design Studio > Application > Scheduler.
Filter and locate the Scheduler configured during Mailbox setup.
Click Scheduler run immediately and refresh until the job displays Success.
Login as an Analyst.
Navigate to Manage Incident List page.
Verify if the tickets are created for all sent emails.
N/A
79604
In the Notification Parser, a warning message for mandatory values displays even though all values are entered.
Prerequisite:
A Filter is configured in the Define Condition step under Parser Content, where the User-Defined Key is set to Symptom, the Operator is Set to contains, and the value is set to Automation.
Steps:
Log in to the application as an Application Designer.
Navigate to Application Tile > Notification Parser.
Click the ID hyperlink of Mail to Incident parser from the list.
Click Parser Content step and delete all the Line Form entries that were previously added.
Observe that the filter in Define Conditions remains and click Next.
N/A
79461
In the Mailbox Configuration, the warning message 'You have not entered all mandatory value(s).' displays even though all mandatory values are provided in the mail to create a ticket using the API.
Steps:
Log in to the application as an Application Designer.
Navigate to Application Tile > Mailbox Configuration.
Click New and enter the required details. Click Next in the Configuration and Rules steps.
N/A
79328
The value is not getting binded for ‘Tree View’ control.
Steps:
Log in to the application as an End User.
Navigate to My Incidents and raise an incident.
Log in to the application as an Analyst.
Click on the above-created Incident ID hyperlink. The Incident Details page is displayed.
Observe the value for Category field.
N/A
79412
On the Manage Incidents – Details page, a field-level inline message displays when the user uploads multiple files one after another in the Attachment control. However, the inline message does not display when the user uploads multiple files simultaneously.
Steps:
Login to the application as an Analyst.
Navigate to Service Management > Incidents > Manage Incidents. The Manage Incidents - List page is displayed.
Click New from the Manage Incidents - List page.
Enter the required details and attach the file in Attachment field one by one with file up to 24MB.
Verify the field level inline which will be displayed.
N/A
90353
In the User Incident Details page, for Category and Classification fields the value is not getting binded. After page refresh the value gets binded.
Prerequisite:
Incident should be created.
Scenario 1:
Login as End User and navigate to My Incidents list page.
Click on the Pending tab and then click on In Progress tab.
Click on the ID link of the record.
Verify whether the value is populated for Category & Classification fields.
Scenario 2:
Login as End User and navigate to My Incidents list page.
Click on the ID link of the record.
If the value is populated for Category & Classification field, then follow the below step.
Click on the Update Incident icon.
Enter the Message and click on Save button.
Then, verify whether the value is populated for Category and Classification fields.