The multiple uploaded attachments were not displayed.
Steps:
Log into the application as an End User.
Select the application as Service Request.
Navigate to Request > My Service Request.
Existing Catalog must have File Upload control with Allow Multiple Attachment.
Raise an SR by uploading multiple attachments.
Log in to the application as an Analyst.
Navigate to Manage Service Request - Catalog Details page and verify if all the uploaded attachments are displayed.
The multiple uploaded attachments are getting displayed.
174570
After clicking New, the page was not loading for few seconds.
Steps:
Log in to the Apex application as an Analyst.
Navigate to Service Request > My Service Requests. The My Service Request list page is displayed.
Click New. Observe the duration of page load.
After clicking New, the page is loading without any delay.
175438
In an SR, duplicate attachments were displayed under the Description field when a Category was selected or changed.
Steps:
Log in to the Apex application as an Analyst.
Navigate to Service Request > Manage Service Request > Service Request List. The Service Request List page is displayed.
Click New and in the General tab, select a Tenant.
In the General tab, upload an Attachment.
Example: Uploading one file displays Attachment (1) in the Description field.
Select Category, verify the attachment count displayed in the Description field.
The Attachment count is displayed correctly under the Description field of the SR when a Category is selected.
175487
When an SR was created from an Incident and a new file is attached, the file is not uploaded, and an error message was displayed: Invalid file size. Maximum upload size is 25 MB.
Steps:
Log on to the Apex application as an Analyst.
Navigate to Incidents > Manage Incidents > Manage Incident List. The Manage Incident List page appears.
Click New, attach a file, and create an Incident. Click Save.
Navigate to the Links tab.
Click Create > Service Request.
On the SR Details page, click the Attachment Control and select a new file.
Verify that the file is uploaded successfully.
When an SR is created from an Incident and a new file is attached, the file uploads successfully and a confirmation message is displayed.
171769
In the Send Email functionality, emails were not triggering when the To field in the Recipient section contained By Roles.
Steps:
Log in to the Application as an Analyst.
Navigate to Service Management > Incident > Manage Incidents. Manage Incidents – List page is displayed.
Select Incident ID to send an email.
Click on the Send Email icon in the Incident.
In the To field select By Roles and enter other details.
Click Submit and verify if an Email is sent.
Emails are sent when By Roles is selected in the To field.
176488
Post-upgrade, the created fields with Common Master configuration (parent and child) relationship were not displaying values.
Steps:
Create two fields and configure Common Master with parent and child relationship.
Post-upgrade, the created fields with Common Master configuration (parent and child) relationship are displaying values.
176540
The Common Master values for Root Cause Failure Code and Subcode were not displayed in the RCA tab and displayed blank.
Prerequisite:
Configure a new Common Master in the Incident Form and add values to it.
Steps:
Log in to the Apex application as an Analyst.
Navigate to Incident > My Incidents.
Click New from the Incident List page.
Select a Tenant from the dropdown.
Click the configured Single Choice control and verify whether values are displaying in the dropdown.
The configured Common Master values display without issues.
176193
Re-accessing the SSO-enabled URL without completing login resulted in a blank page instead of redirecting to the authentication page.
Prerequisite:
Configure SSO configuration.
Steps:
Type the SSO enable URL in the browser.
Verify if redirects to the SSO page for authentication.
SSO enabled URL redirects to the SSO page without any issue.
Known Issues in Crescendo 6.3.1.1 Patch 12
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.
N/A
Was this article helpful?
Thank you for your feedback! Our team will get back to you
