Release Notes Crescendo SP1 (6.3.1.1)

79604

A warning message for mandatory values is displayed despite all the values being entered on existing notification parser.

Prerequisites:

A filter is added in the "Define Condition" section under Parser Content using:

1. User Defined Key: Symptom  

2. Operator: contains  

3. Value: Automation

Steps:

1. Log in to the application.

2. Go to Settings → Design Studio → Application Tile.

3. Navigate to Notification Parser.

4. Open the "Mail to Incident" parser from the list.

5. Go to the "Parser Content" stepper.

6. Delete all the Line Form entries that were previously added.

7. Observe that the filter in "Define Conditions" remains.

8. Click the Next button.

N/A

79381

Record is getting created using workflow but created records is not displaying in links tab.

Prerequisite:

Workflow must be configured.

Steps:

1. Log in to the application.

2. Navigate to Service Management > Incidents > Manage Incidents.

3. Click New button on the list page.

4. Fill all mandatory details.

5. Attach file in the Attachment field.

6. Click Save.

7. Access the same by clicking on ID hyperlink.

8. Navigate to Links tab and verify created record using workflow is present in the Links tab.

N/A

79445

Notification Email is not triggering to Power Approver.

Prerequisite

Workflow must be configured with Enable Special Approver.

Steps:

1. Log in to the application as App Designer.

2. Drag and drop Notification component on the Canvas.

3. Navigate to Properties popup.

4. Choose medium as Email, Notification Template.

5. Choose To = Power Approver.

6. Save Notification component.

7. Save and Publish the workflow.

8. Raise a record matching the workflow.

9. Check if the email notification is sent to Power Approver.

N/A

79454

When Level 1 approver or Special approver ‘Refer Back’ to Requestor then Notification Email is not triggered to Requestor.

Prerequisites

1. Configure the workflow with Enable Special Approver=Yes, Dynamic.

2. In the workflow, configure the ‘Refer Back’ option.

Steps

1. Navigate to Manage Change Record list page.

2. Raise a record matching the workflow conditions.

3. Log in as Level 1 approver or Special approver.

4. Click Approve button and choose Refer Back to Requestor.

5. Verify if the workflow is restarted.

6. In the Approval Timeline - Tabular view, verify the Refer Back details.  

N/A

79582

Form Relation: Tree View - navigate to saved Form relation - in Map Values popup, selected parent node to parent node value - row is displayed twice.

Prerequisite

In form designer, configure tree view and in advance tab, enable the 'Allow Selection of Parent Node' switch

Steps

1. Navigate to Form relation.

2. Open existing form relation, Navigate to Map fields stepper.

3. Navigate to tree view map values popup.

4. Select the Parent node in source and select parent node as in target field.

5. Submit the map values popup.

6. Save the Form Relation.

7. Again, open the saved form relation, navigate to Map fields stepper.

8. Navigate to Tree view map values popup.

9. Verify that selected values are retained.

10. Selected parent node to parent node value row is displayed twice.

N/A

171497

The record count in the exported Excel file did not accurately reflect the number of records exported.

Steps:

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

2. Navigate to the Workgroups > Manage Workgroup list page.

3. Click Export to Excel icon. Select the option Export Current Page.
   

4. The records get exported to a downloadable excel file.

5. Observe the number of exported records in the excel file.

The record count in the exported Excel file is accurately reflecting the number of records exported.

170348

When using Form-Defined attributes for the sequence generator, it was not displaying the attribute values along with the Sequence ID.

Steps:

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

2. Navigate to Sequence Generator tab under Form Designer. Configure ID Format using Form-Defined attributes.

3. Publish the form.
   

4. Log in to the Apex application as an End User and navigate to the Manage Incidents List page.

5. Observe the auto-generated Sequence Ids on the list page.

When using Form-Defined attributes for the sequence generator, it is displaying the attribute values along with the Sequence ID.

171561

Users could not log in to the SSO instance when using Incognito Window.

Steps:

1. Click the Start Menu (Windows icon at the bottom-left corner).
   

2. Type the name of the browser.
   

3. Click browser name when it appears in the search results.
   

4. Click three-dot menu (⋮) in the top-right corner.
   

5. Select New Incognito Window.
   

6. Enter SSO Apex Instance on the browser textbox and click Enter.
   

7. Enter the required credentials and click Submit.

The user can log in to the SSO Apex instance using an Incognito Window without any issues.

171494

The Tenant displayed an incorrect record count after the filter was applied to the Workgroup List View page.

Steps:

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

2. Navigate to Application tab > Workgroup.
   The Workgroup list page is displayed.

3. Click Filter icon and configure to filter the list page details.  

4. Update the Workgroup's 'Active' status and apply the corresponding filter to verify the count. Similarly, modify the 'Default' and 'Master' statuses to ensure filters work correctly in all cases.

The record count on the Workgroup list page is displayed correctly after applying a filter.

171351

In Incident Management, analysts could not attach files more than 5 MB.  

Steps:

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

2. Navigate to Service Management > Incident > Manage Incidents.

   The Manage Incidents list page is displayed.  
   

3. Click New to create an Incident. Enter all the mandatory details.
   

4. Attach files more than 5MB and save the incident.  

Analysts are able to attach files larger than 5 MB and a maximum of 25 MB.  

170332

Resolution SLA Remaining Time was displaying incorrectly for a few tickets on the Manage List page.

Resolution SLA Remaining Time is displaying correctly on the Manage List page.

171234

Issue 1:  

The Wait for Condition step was not triggered during Service Request approval when the control is placed in a Sub Form and its value is updated on the approval page

Issue 2:

The Switch component in the Workflow was not evaluated when the control is placed on a Sub Form.

Issue 3:  

The Specification details under Approve Service Requests page were not getting saved.  

Prerequisite:  

Create a Service Request that includes a configured approval workflow.

Steps:

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

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

3. Click any existing SR ID hyperlink.  

4. On the Approve Service Requests – Details page, navigate to Catalog Details tab.  

5. Under Specifications, fill in the required details and click Save.

6. Verify whether all the details are saved.

Issue 1:  

The Wait for Condition step is successfully triggering during Service Request approval.  

Issue 2:  

The Switch component in the Workflow is evaluated when the control is placed on a Sub Form.  

Issue 3:

The Specification details under Approve Service Requests page are saved successfully.  

169877

Workflow was not triggering when users created Service Request from Manage SR form via Call module.

Workflow is triggering when users create Service Request from Manage SR form via Call module.

167864

In the Incident module, on the Form Relations user had set the Target Module field as Incident for the WO form in the IM to WO form relation, but while creating the WO from IM, it was not setting any value.

While creating WO from IM, values are setting according to the configuration in the Form Relation.

169527

The filter wasn't applied correctly and required a page refresh or navigating to a different page to display the selected view.

The filter application works fine and displays the results as per the selected criteria. 

169680

The assigned analyst encountered an issue when an End User attached a file while submitting a Service Request.

The Analyst could not resolve the Service Request from the Manage Service Request page due to an error message indicating that something went wrong.  

Prerequisites: 

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

2. Navigate to Design Studio > Service Request > Select Sub Form (Catalog).
   

3. Go to Publish step and change the status to Maintenance and click Submit.
   

4. Configure attachment control for the Catalog form.
   

5. Publish the Form. 

Steps: 

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

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

3. Create a Service Request with the same Catalog. Attach any attachment to the Service Request.  
   

4. Log in as an Analyst.  
   

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

6. Click the SR ID created by the End User. SR Details page is displayed.  
   

7. Update or Resolve the Service Request. 

The assigned analyst can resolve the Service Request which has a file attached by End User.  

171316

Change Blackout Window was not working as expected.

Change Blackout Window configuration works as expected.

168956

The Workflow was mapped, and Work Orders were generated as expected. However, the Service Request (SR) was not automatically resolved upon completion.

Steps:

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

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

3. Click the SR ID for which the Workflow is mapped, and Work Order is configured.

4. Navigate to Links tab and click Work Order. Observe the status of the SR ID.

Service Request (SR) is automatically resolved upon completion.