Crescendo 6.3.1.2 Patch 7

177340

The Login page was not getting displayed and it was appearing blank.

Steps:

1. Log in to the Apex application.
   

2. After session time out, close the tab.
   

3. Trigger the instance URL in a different tab.

The Login page is getting displayed.

179125

After email parsing, emails were not moving to different folder.

Steps:

1. Navigate to Service Management > Mailbox Configuration > Add Mailbox. The Configure Rules for Mailbox pop-up is displayed.

2. Select Move to Folder option to move processed emails to different folders.

After email parsing, emails are moving to different folder.

180006

In the Apex application, the Pending Reason and Status fields were displayed with empty values.

Steps:

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

2. Navigate to Service Request > Manage Service Requests.
   

3. Click New.
   

4. Verify if the Pending Reason value are displayed with empty values.

In the Apex application, the Pending Reason and Status fields now display values without any issues.

179521

The Apex application did not authenticate through SSO in incognito mode. After the user attempted to sign in, the SSO flow redirected to the form-based login page instead of completing SSO.

Steps:

1. Open Microsoft Edge browser.
   

2. Enter the Apex application web address in the Microsoft Edge text box.
   

3. Verify if the web address redirects to the SSO login.

The Apex application now authenticates through SSO in incognito mode. The SSO flow completes successfully without redirecting the user to the form-based login page.

180148

Users were unable to submit incident tickets from My Incidents page, on submission users were experiencing an error as “Something went wrong”.

Prerequisites:

1. Add 2 File Upload controls in My Incident form.
   

2. In one of the File Upload controls configure the below Validation rule and Publish.
   Additional Attachments should be Mandatory When Below Condition Meet.
   
   Attachment is not empty.
   

Steps:

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

2. Select Service Management.

3. Navigate to Incident > Manage Incidents > My Incidents.
   List page is displayed.

4. Click New to create an Incident.

5. Enter all the details and click Save.

6. Verify if you can submit the request successfully.

Users are able to submit incident tickets from My Incidents page successfully.

178195

When users mapped Approval Type based on the User Attribute workflow then, that workflow was not triggering from the new request.

Steps:

1. Log in to the application as an Analyst.

2. Configure Workflow with Approval Type = Based on User Attributes.

3. Create a new request.

4. Verify if the workflow is triggered for the request.

When users mapped Approval Type based on User Attribute workflow then, that workflow was triggering from the new request.

179666

The links in incident notification emails were not working correctly — they redirected to the default dashboard instead of the Incident Details page.

Steps:

1. Click click here hyperlink in Incident Notification email.
   

2. Observe the redirecting page on click here hyperlink.

The links in incident notification emails are working correctly and redirecting to Incident Details page.

179967

Due to cache refresh users were unable to see correct information on List or details pages.

Steps:

1. Log in to the application as an Analyst.
   

2. Update the latest Web.Config file with changes related to env.js
   

3. Refresh the Angular app pool.
   

4. Clear the cache & browser history (Since Old cache is still active).
   

5. Login to Application and verify the Build No.
   

6. Navigate to env.js and update the new Build No.
   

Verify the below:

• Click F5 or click on Refresh Icon in the browser and verify whether the latest Build No is displayed.

• Logout and Login back and verify whether the latest Build No is displayed.

Users are able to see correct information on List or details pages after fixing the cache mechanism.

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