Login
    Contents x
    Crescendo 6.3.1.2
    • 30 Sep 2025
    • 9 Minutes to read
    • Print
    • PDF
    Contents

    Crescendo 6.3.1.2

    • Updated on 30 Sep 2025
    • 9 Minutes to read
    • Print
    • PDF
    Article summary

    New Features

    There are no new features for this release. 

    Fixed Issues

    Issue ID

    Issue Description

    Scenario

    Resolution

    177730

    In the Workflow Approval component, the configured Forward To approval action did not function.

    Steps:

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

    2. Navigate to Design Studio > select a module > Workflow Designer.
      The Workflow Designer list page is displayed.

    3. Click New to enter the required details and click Save > Next.

    4. In the Set Trigger & Conditions step click Save and click Next.

    5. In the Design Workflow step, drag and drop the User Approval component into the canvas.

    6. Double-click the User Approval component, enter the required details, and enable the Forward To approval action.

    7. Verify if the Forward To is associated with User Approval component.

    The Forward To approval action is working without any issue.

    177868

    A '500 Internal Server Error' message was displayed when an Asset was allocated through the API.

    Steps:

    1. Log in to the application as an Administrator.

    2. Navigate to Platform Studio > API Hub > Explorer.

    3. Click Update a Record (PUT) and enter the required details with required API.

    4. Click Send.

    The Asset is allotted without any issues.

    178030

    The multi-choice field created in the Catalog was displayed on the Manage SR page but was not displayed in the API Explorer.

    Prerequisite:

    Create a Catalog and add a Multi-Choice field in the Form.

    Steps:

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

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

    3. Click New and select the Catalog to enter the required details.

    4. Click Save.

    5. Log in to the application as an Administrator.

    6. Navigate to Platform Studio > API Hub > Explorer.

    7. Enter the required details and verify the Multi-Choice field.

    The configured Multi-Choice field in the Catalog is displayed in the API Explorer without any issue.

    177622

    Duplicate values were displaying in the Single Choice field.

    Steps:

    1. Create a new Catalog form.

    2. In the form designer, add a Single Choice field.

    3. Set the data source to Manual, add the values, and publish the form.

    4. Log a Service Request the above Catalog.

    5. Validate if the Single Choice field displays duplicate values.

    Duplicate values are not displaying in the Single Choice field.

    171441

    The Status field value was populating the Requestor field value.

    Steps:

    1. Log in to the Application as an Analyst.

    2. In the Advanced Filter, select request field operator 'is' then select any value.

    3. Select Status field operator 'is one of' then select multiple values.

    4. Save as a View.

    5. Click on the Filter.

    6. Click request field value dropdown (don't select any value, just click the dropdown).

    7. Click Status field value dropdown and validate.

    The Status field value is populating as expected.

    175977

    The GDPR consent form was displayed after user login.

    Steps:

    1. Log in to the Apex application.

    2. Validate if the GDPR consent form is displayed.

    The GDPR consent form is not displaying after disabling it in the app config.

    174719

    After the Bulk Update, the Solution field for the incident was displaying improper values.

    Steps:

    1. Navigate to Incident Management > Manage Incidents. The Incident List page is displayed.

    2. Select the required incident and perform Bulk Update action.

    3. Observe the Solution field value for the bulk updated incidents.

    After the Bulk Update, the Solution field for the incident displays proper values.

    174227

    Approval Notification was not getting triggered to Level 2 Approvals.

    Steps:

    1. Configure a workflow on Sub Form with 2 level of approvals.

    2. Raise an SR.

    3. Verify whether the approval notification is triggered to Level 1 approval.

    4. Login as Level 1 approver and approve it.

    5. Verify whether the approval notification is triggered to Level 2 approval.

    Approval Notification is getting triggered to Level 2 Approvals.

    177335

    When connected through VPN, scripts and configurations load indefinitely, resulting in improper data transfer or access over the VPN.

    Steps:

    1. Log in to the application via VPN.

    2. Observe the loaded page with data values.

    When connected through VPN, no issues for data transfer or data access.

    169442/169379

    The Refresh Interval time was not taking effect after saving or logging back to the application.

    Steps:

    1. Log in to the Application as an Analyst.

    2. Navigate to Incident > Manage Incidents.
      Note: You can select any of the consumer forms, such as My Incidents, Manage service requests, etc.

    3. Enable Refresh Interval in any of the consumer forms (Example: My Incidents, Manage service requests).

    4. On the consumer end, click on the Refresh Interval icon, set the number of minutes, and click on the Save button.

    5. Navigate to any other page and return to the List page or open any record by clicking on the Incident ID hyperlink.

    6. Again, come back to the list page and click on the Refresh Interval icon and verify whether the value being set is retained or not.

    Refresh Interval time is working as expected after saving or by logging into the application.

    176040/176046

    Users were experiencing an Error while clicking on the Export All option on the Manage Incidents List page.

    The following error message was displayed: “There was an error processing your export request. Please try later”.

    Steps:

    1. Log in to the Application as an Analyst.

    2. Navigate to Incident > Manage Incidents.

    3. Click on the export icon (apply filters and records per page to a value between 45 and 50).

    4. Perform Export all and Export current page functionality.

    5. Export ALL and verify.

    Users are able to Export All from the Incident list page successfully.

    177505

    In the Catalog form, users used Single Choice fields with the User reference field as the Data Source to display the Requestor’s city and country. The fields worked correctly in the form UI, but they were not functioning as expected when accessed via the API.

    Steps:

    1. Log in to the Application as a Designer.

    2. Create a new form for Catalog and add a Single Choice field. Configure the Single Choice field with the following values:

      Data Source: Table Table: Platform User Layer: City
      Parent: Requestor
      Filter Column: Unique ID

    3. Save the form.

    4. Create a new record through the API Explorer.

    5. Validate the City value.
      Note: It must not display as an email value.

    Single Choice fields work as expected when a new record is created through the API.

    174641

    Updated details were missing in the Timeline tab of the Incident.

    Steps:

    1. Log in to the Application as an Analyst.

    2. Navigate to Incident > Manage Incidents.

    3. Open the required incident.

    4. Change the Workgroup and Submit the Incident.

    5. Open the same Incident, navigate to the Timeline tab, and verify the timeline.

    Updated details are displaying in the Timeline tab after saving the Incident.

    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

    Was this article helpful?
    What's Next
    Change password!
    Changing your password will log you out immediately. Use the new password to log back in.
    Change profile
    Success!
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.
    Logout
    ESC

    Eddy AI, facilitating knowledge discovery through conversational intelligence