Crescendo 6.3.1.2 Patch 8

180784

The Manage Service Requests list displayed only one Service Request instead of thirty, and in another instance, it showed ‘No data to display.

Steps:

1. Log in to an application as an Admin.
   

2. Navigate to Manage Service Requests > Service Request List.
   The Service Request List page is displayed.
   

3. Select Non Default View, go to the My Service Requests page a few times and then return to the Manage Service Requests page.
   

4. Verify list of Service Request.

The Service Request List displays the correct count without any issues.

180165

On the Manage Service Requests page, the Service Catalog validation controls are not functioning correctly on page load.

Prerequisites:

1. Create a Service Catalog with validation controls.
   

2. Create a SR with the created Service Catalog.

Steps:

1. Log in to an application as an Analyst.
   

2. Navigate to Manage Service Requests > Service Request List.
   The Service Request List page is displayed.
   

3. Click SR ID hyperlink of the previously created SR.
   

4. Verify the created validation control.

The validation control are working without any issues.

180717

Only the header row was displayed in the exported file without any data.

Steps:

1. Log in to the Apex application using an L2 Support ID.
   

2. Navigate to Manage Incidents. The Manage Incidents List page is displayed.
   

3. Change the default view from “NP Test Default” to “17112025”.
   

4. Change the Show Count from 20 to 40.
   

5. Export the Report to an excel sheet.

The exported file displays the data as well along with header row.

180165

Validations provided at Validation Tab while designing the catalog was not working as expected.

Steps:

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

2. Configure Validations using Form Designer > Design > Validations.
   

3. Publish the Form.
   

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

5. Navigate to Service Requests > Manage Service Requests – List page.
   

6. Observe the validations configured for the catalog.

Validations provided at Validation Tab while designing the catalog was not working as expected.

178861

The values for the Response SLA and Resolution SLA fields were not appearing on the list page, even though they have been added to the default columns and SLA breach data.

Steps:

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

2. Configure Response SLA and Resolution SLA fields as default columns and SLA Breach Data.
   

3. Observe the values of Response SLA and Resolution SLA fields on the list page.

The values for the Response SLA and Resolution SLA fields are appearing on the list page, after adding to the default columns and SLA breach data.

180613

The Close icon was not appearing in the Data Source while creating the Dashboard.

Steps:

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

2. Navigate to Service Management > Dashboard Designer > Dashboard Menu > Data Sources.
   

3. Observe the closing of Dashboard Menu using Close icon.

The Close icon is appearing in the Data Source while creating the Dashboard
.

180719

In Asset Ordering Catalog, after triggering the Workflow, the first Workorder is created, however second Workorder was not getting created even after resolving.

Steps:

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

2. Trigger the first Workflow for Asset Ordering Catalog, and resolve it.

3. Observe the creation of second Workorder.

In Asset Ordering Catalog, after triggering the Workflow, the first Workorder is created, and second Workorder is also getting created after resolving.

180785

The system was displaying a message as “No data to display” though the relevant records existed in the view.

Steps:

1. Log in to the application as an Analyst.
   

2. Navigate Service Request > Manage Service Request.
   List page is displayed.
   

3. Click on different Status options.
   

4. Again, navigate to Manage Service Request.
   

5. Select the different view options. and verify.
   

Note

Repeat for Incident module to verify.

The system is not displaying message as “No data to display” upon selecting the View on the list page.

180495

Manage Service Request list was exporting incorrect data to the Excel export.

Steps:

1. Log in to the application as an Analyst.

2. Navigate to Request > Manage Service Request.
   List page loads the default view with 8 counts.

3. Log out and then log in to the application.

4. It loads the default view on the Manage Service Request page.

5. Click Export.

6. Verify if the data is correct.

Manage Service Request list is exporting correct data to the excel sheet.

180491

Manage Service Request list was exporting incorrect data to the Excel upon selecting Export All on the list page.

Steps:

1. Log in to the application as an Analyst.

2. Navigate to Service Request > Manage Service Request.

3. Data from the default view is displayed.

4. Select any alternate view.

5. Select Default View again.

6. Log out and log in to the application.

7. Navigate to Service Request > Manage Service Request.

8. Data from the default view is displayed.

9. Click Export All.

10. Verify if partial data is exported to the Excel.

Manage Service Request list is exporting correct data to the Excel upon selecting Export All from the list page.

180489

Filters were not loading the details on the Manage Incident list page upon selecting the Filter View. Multiple views for the selected value that belong to View was displaying Blank.

Steps:

1. Log in to the application as an Analyst.

2. Navigate to Incident > Manage Incidents.
   Data from the default view is displayed.

3. Select any alternate view.

4. Select Default View again.

5. Log out and log in to the application again.

6. Verify if the Filter View is displaying values.

Filters on the list page is working as expected.

180718

The Manage Incident list displayed 'No data to display' despite the presence of valid records.

Steps:

1. Log in to an application as an Analyst.
   

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

3. Verify the Manage Incidents – List page even when valid records are present.

The Manage Incidents - List displays the available records without any issues.

179512

The Resolution SLA columns, added in the Form Designer’s Design List View step, were not displayed in the Manage Incident list page for users..

Prerequisite:

Configure a form in Form Designer with Resolution SLA columns and publish it.

Steps:

1. Log in to an application as an Analyst.
   

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

3. Click New and enter the required details.
   

4. Verify the Resolution SLA columns.

The Resolution SLA related columns such as Resolution SLA Elapsed Time, Total Time, Deadline, and Remaining Time are available to add in the Manage Incident List page without any issue.

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