Crescendo 6.3.1.2 Patch 2

178340

On the Manage Service Requests - Details page, the Requestor field did not populate the requestor name by default.

Steps:

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

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

3. Click SR ID hyperlink.
   

4. Click Catalog Details tab.
   

5. Verify the Requestor field.

The Requestor field displays the requestor name without any issues.

178863

While updating efforts in Hours field it was captured in days.

Steps:

1. Log in to the application as an Analyst.
   

2. Navigate to Service Management > Incident > Manage Incidents.
   Manage Incidents list page is displayed.
   

3. Click the required Incident ID hyperlink to view the Incident.
   

4. Add the Efforts in Hours. Save the record.

5. Verify the Efforts.

Efforts in the Hours field is capturing as expected.

178247

Users were still able to select the parent node Category.

Prerequisite:

Disable the selection of Parent Node.

Steps:

1. Navigate to Service Management > Module > Problem > Manage Problem Records. The list of Problem Records is displaying.
   

2. Click the Problem Record ID hyperlink.
   

3. The Problem Record Details page is displayed.
   

4. Select the Category.
   

5. Observe the selection of the parent node.

Users are not able to select the parent node Category.

178722

System displays the following error:

“An error occurred while processing your request.”

Steps:

1. Log in to Apex Application as an App Designer.
   

2. Navigate to Service Management > Service Request > Design Studio > Form Designer.
   

3. Enable the Tenant in Classification Admin Form.

System does not display any error while putting the form under maintenance or enabling the Tenant.

178247

Notifications were not sent for few incidents.

Steps:

1. Navigate to Service Management > Scheduler > New.
   

2. Configure Notify Recipients under Actions.

Notifications are being sent for all incidents.

178821

On the Approve Service Requests – List page, the Reports option was displayed when the delegated user switched to the primary user account.

Prerequisite:

Configure a Delegate Rule for SR approval to approve on behalf of the primary user.

Steps:

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

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

3. Verify the Reports option on the left panel.

The Reports option is not displayed when logged in as an approver.

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

The Analyst Dashboard is experiencing significant performance delays. It takes over 36 seconds to fully load the page after selection. This loading time negatively impacts usability and efficiency for analysts working within the system

Steps:

1. Log in to the Application.
   

2. Navigate to Service Management.
   

3. Access the Analyst Dashboard.

N/A

91561

RCA Required’ Toggle Briefly Appears Then Disappears on Major Incident Popup.

Steps:

1. Log in to the Application.
   

2. Navigate to Incident > Manage Incident List.
   

3. Open any existing incident.
   

4. Enable RCA Required toggle.

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