Crescendo 6.3.1.2 Patch 9

180314/ 178517

In IM and SR, the application did not retain the submitted CSAT Feedback. When the feedback option was reopened, the previously entered data was missing, and the reports showed no feedback received despite the submissions.

Prerequisite:

Create and resolve an Incident.

Steps:

1. Log in to the application as an Analyst.
   

2. Navigate to Incident > My Incidents.

   The My Incidents – List page is displayed.
   

3. Click Incident ID hyperlink of the resolve incident.
   

4. Click Provide Feedback icon and provide the feedback and save the details.
   

5. Verify if provide feedback is displayed after reopening the incident.

The CSAT Feedback submitted for the incident is displayed without any issue.

181073

Upon removing the Filter on the Incident List page, Export to Excel function was not exporting the correct data.

Steps:

1. Log in to the application as an Analyst.
   

2. Navigate to Incident > Manage Incident. Incident List page is displayed.
   

3. Default View is displayed.

4. Click Export to Excel and validate the records.
   

5. Click Filters and remove the Fields in the Filter.
   

6. Click Export to Excel and validate the records.

Export to Excel function is working as expected after removing the Filter option on the Incident List page.

180590

Users were experiencing an error as “this value already exists” upon creating child values in the Common Master.

Prerequisite:

Create a new master type and ensure Parent Type is selected.

Steps:

1. Log in to the application as an Admin.
   

2. Navigate to Platform Studio > Platform Masters > Common Master.
   

3. Click Add Master Type.
   

4. Select Master Type and validate the Master values configured.
   

5. Select Allocation Type and verify the count.
   

6. The value must display for only the selected Allocation Type.

Users are able to create child values in the Common Master successfully.

180840

The Refer Back status was not getting updated as soon as the Approver selected status as Refer Back and at the same time BR was getting failed.

Steps:

1. Log in to the Apex application as an Approver.
   

2. In the Workflow Approval section select the status as Refer Back.
   

3. Click Submit.

The Refer Back status is getting updated as soon as the Approver selected status as Refer Back and at the same time BR is also executing.

180214

The User Profile card was not displaying any valued for the configured Department field.

Steps:

1. Log in to the Apex application as an App Designer or Admin.
   

2. Navigate to Platform Studio > Access Control Center > User.
   

3. Configure Department field under General tab.
   

4. Observe the configured Department value for User Profile card.

The User Profile card displays the value for the configured Department field.

170054

The Cancelled SR was still getting displayed under Notifications.

Steps:

1. Log in to the Apex application as an Analyst.
   

2. Navigate to Service Management > My Service Request List page.
   

3. Click the SR ID hyperlink.
   

4. Click Cancel icon to cancel the SR.
   

5. Navigate to Navigate to Service Management > My Service Request List page.
   

6. Click the Notification icon and observe the cancelled SR.
   

7. Click Submit.

The Cancelled SR is not getting displayed under Notifications.
.

180584

Workflow set value was not working as per expectation while same kind of workflow was working in another catalogue.

Steps:

1. Create a new workflow with catalogue table and add one button in main form (Manage SR) for next workgroup set.
   

2. Add set value tile in workflow and add workgroup WG1 and status as New.
   

3. Add another condition of utilities of wait for condition and set next workgroup true.
   

4. Add another set value tile and set Workgroup WG2 and next workgroup false.
   

5. Add another set value tile and set Workgroup WG1.

Workflow set value is working as per expectation.

180716

When an Incident was created from a User Incident, the Source Form status did not change to Pending as expected.

Prerequisite:

Configure a Form Relation with Set Values as:

• Field -Priority

• Status – P1 - High

• Field – Status

• Status – Pending

Steps:

1. Log in to the application as an Analyst.
   

2. Navigate to Incident > My Incident. The My Incidents – List page is displayed.
   

3. Click Incident ID hyperlink of the resolve incident.
   

4. Chang the Priority to P1 - High.
   

5. Navigate to Link tab and create a SR and Priority as P1 – High.
   

6. Verify the Incident and SR status.

SR status is changing without any issue on creating through Create Link tab.

84144

Users are not able to create the duplicate Priority Matrix.

Steps:

1. Login to the application as an Application Designer.

2. Select Service Management application.

3. Click on settings icon and select the Module as Problem.

4. Navigate to Configuration > Priority Matrix.

5. Select already existing field value for the Impact, Urgency, Priority fields.

6. 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:

1. Login to the application as an Analyst.

2. Navigate to Service Management > Incidents > Manage Incidents.

3. Click New button on the list page.

4. Fill all the mandatory details.

5. Upload the file in Attachment field.

6. Click on Save button.

7. Access the same created by clicking on ID hyperlink.

8. Navigate to Links tab and click on Create button and select the module for which form relation is configured (Example: INC to SR.)

9. Verify the uploaded file in Attachment field.

10. Click Save button and verify whether user can save the Target Form (SR).

11. Verify the toast message.

NA

79372

Users are experiencing alignment issue in the Create tab of Links tab in the Form Designer.

Steps:

1. Log in to the application as an Application Designer.

2. Navigate to Service Management > Design Studio > Select Module as Incident > Form Designer.

3. Select Manage Incidents form and place the form in Maintenance.

4. Navigate to Design Form step.

5. Click on the gear icon of Links tab.

6. 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:

1. Log in to Apex application.

2. Select Service Management application.  

3. Navigate Problem > Manage Problem Record. The Manage Problem Record List page is displayed.

4. Click existing PR ID and navigate to Links tab.

5. Select Incident or SR. The Link pop-up appears.

6. 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:

1. Log in to the Apex application.

2. Navigate to Settings > Design Studio > Application > Notification Parser. The Notification Parser List is displayed.

3. Click New and fill in all mandatory fields.

4. Navigate to the Parser Content step. Fill in all required Line Form entries.

5. To add or update form data, select the relevant line form and configure the Define Keys.

6. Select Define Conditions step.

N/A

78560

Only one email was converted into a ticket. The remaining emails were not processed or converted.

Prerequisites:

1. API Configuration is set up

2. Mailbox is configured correctly

3. Notification Parser is configured

Steps:

1. Log in to the application as an Admin.

2. Navigate to Design Studio > Application > Scheduler.

3. Filter and locate the Scheduler configured during Mailbox setup.

4. Click Scheduler run immediately and refresh until the job displays Success.

5. Login as an Analyst.

6. Navigate to Manage Incident List page.

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

1. Log in to the application as an Application Designer.
   

2. Navigate to Application Tile > Notification Parser.
   

3. Click the ID hyperlink of Mail to Incident parser from the list.
   

4. Click Parser Content step and delete all the Line Form entries that were previously added.
   

5. 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:

1. Log in to the application as an Application Designer.
   

2. Navigate to Application Tile > Mailbox Configuration.
   

3. 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:

1. Log in to the application as an End User.

2. Navigate to My Incidents and raise an incident.

3. Log in to the application as an Analyst.

4. Click on the above-created Incident ID hyperlink. The Incident Details page is displayed.

5. 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:

1. Login to the application as an Analyst.
   

2. Navigate to Service Management > Incidents > Manage Incidents.
   The Manage Incidents - List page is displayed.
   

3. Click New from the Manage Incidents - List page.
   

4. Enter the required details and attach the file in Attachment field one by one with file up to 24MB.
   

5. 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:

1. Login as End User and navigate to My Incidents list page.

2. Click on the Pending tab and then click on In Progress tab.

3. Click on the ID link of the record.

4. Verify whether the value is populated for Category & Classification fields.
   

Scenario 2:

1. Login as End User and navigate to My Incidents list page.

2. Click on the ID link of the record.

3. If the value is populated for Category & Classification field, then follow the below step.

4. Click on the Update Incident icon.

5. Enter the Message and click on Save button.

6. Then, verify whether the value is populated for Category and Classification fields.

N/A

81008

Problem record status not reflected in linked Incident/SR; Parent-Child option missing in Link Service Request and Link Incident popup.

Steps:

1. Log in to the Apex application as an Analyst.
   

2. Navigate to Service Management > Select the module as Problem.
   

3. Navigate to Problem > Manage Problem Records. The Problem Records List page is displayed.
   

4. Click Problem Record ID hyperlink. The Problem Record Details page is displayed.
   

5. Navigate to Links Tab > Click Link drop-down. Select the Module as Service Request or Incident.
   

6. Observe the Status of the Problem Record on the displayed pop-up.

N/A

91051

The RCA Required toggle switch still appears for a moment on Major Incident pop-up.

Steps:

1. Navigate to Incident. The Incident List page is displayed.
   

2. Click Major Incident ID hyperlink. The Major Incident Details page is displayed.
   

3. Disable RCA Required toggle switch under Prioritization.

N/A

91002

Analyst Dashboard is taking more then 36 sec to load the Page

N/A

91561

Major Incident>‘RCA Required’ Toggle Briefly Appears Then Disappears on Major Incident Popup & Problem Record Not Created on Incident Resolution.

N/A

92737

In the Approval Grid, the Forwarded To user details are not displayed.

N/A

93677

Schedular is getting Failed, when Recipients = AdminTable.Created By or AdminTable.Updated By is configured.

N/A

94140

When Level 1 Approver Rejects the Referred Back request, then in Approval Timeline - Graphical View the approval node is not Highlighted in Red and Workflow Processed is not displayed.

N/A

94153

When Level 2 Approver Refer Back to Requestor and then to Level 1 Approver, in the Approval Timeline the Level 2 node is displayed twice.

N/A

94408

In Data Source tab, when filter is applied then after saving the Value field is not rendered.

N/A