Crescendo 6.3.1.2 Patch 21

  • Updated on Feb 23, 2026
  • Published on Feb 18, 2026
  • 6 minute(s) read
Prev Next

Fixed Issues

Issue ID

Issue Description

Resolution

174189

When you perform an Export All from the Common Master list page, it was displaying an error and not exporting all the Common Master values on the list page.  

You can now perform an Export All from the Common Master list page successfully and export all the Common Master values listed on the Common Master list page.

183266

Despite configuring the blackout Planned Start Time and Planned End Time on Change Blackout Window, and adding the CI to the blackout list, the system continued to allow users to link and edit the CI in CRs without any validation errors.

System does not allow users to link and edit the CI in CRs, if blackout Planned Start Time and Planned End Time on Change Blackout Window is configured and CI is added to the blackout list.

System also displays the following validation message:

“A Change Blackout Window is currently in effect for this CI. You do not have permissions to make changes.”

183305

While searching in the Service Portal on Analyst Dashboard, users had to wait at least one minute for the results to be displayed.

While searching Service Portal on Analyst Dashboard, users need not to wait for the results to get displayed.

184074

When an approver forwarded a Service Request (SR) to another approver, the assigned approver did not see the Approve and Reject action buttons in the notification email template.

When an approver forwards a Service Request (SR), the assigned approver receives the notification with Approve and Reject buttons and can take action directly from the email.

183644

The analyst created four views and opened each in a separate tab. When navigating to the second page in one tab, view 1 incorrectly displayed the second page of View 4 instead of its own data.

Each view retained its own pagination state, and navigating to the second page in one tab did not impact the other open views.

183722

The system did not auto‑close Service Requests (SRs) when all linked Work Orders (WOs) were resolved, nor did it auto‑close SRs when WOs or the SR itself were cancelled. Required hidden fields were missing, and no API‑driven or scheduler‑based automation existed.

The system now uses two APIs (for SR and WO) configured via business rules and schedulers. Hidden fields are added with correct naming conventions. Business rules call the APIs on update, and schedulers auto‑close SRs when WOs are resolved or cancelled.

183722

Work orders were not created as expected in the workflow sequence when the SR was updated. The workflow, configured on a subform, retriggered incorrectly after users selected Update and Refresh Workflow, causing the workflow not to generate the next work order in the sequence. Trigger conditions were not reset, leading to improper workflow behavior.

The workflow now retriggers correctly on SR updates and follows the full sequence to create subsequent work orders. The fix ensures that when Update and Refresh Workflow options are selected, the workflow executes properly, and trigger conditions are reset within the workflow to avoid loops.

Note

Users must not use Update for workflows built on subforms unless trigger conditions are properly configured.

Known Issues

Issue ID

Issue Description

Scenario

Resolution

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