Crescendo 6.3.1.1 Patch 2

171528, 172793

Communication column was not displaying any information.

Steps:

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

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

3. Click Incident ID hyperlink. The Incident ID – Details page is displayed.
   

4. Specify the message under Message > User Communications tab.
   

5. Navigate to Incident > Manage Incidents. The Manage Incident list page is displayed.
   

6. Click Change History. Observe the Communication column.

Communication column is displaying the information.

168701

Analyst with a date format set to dd.mm.yyyy were unable to select a Future Planned Start Time when creating a new Change Record (CR).

Steps:

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

2. Navigate to Change > Manage Change Requests. The Manage Change Requests list page is displayed.
   

3. Navigate to Timelines tab and select the Planned Start Time from the calendar.

Analysts with a date format set to dd.mm.yyyy are able to select a Future Planned Start Time when creating a new Change Record (CR).

171964

All the categories were not visible under Search Category under Service Request.

Steps:

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

2. Navigate to Requests > My Service Requests. The My Service Requests list page is displayed.

3. Select the Tenant as Information Technology.

4. Specify the grandchild Category in the Search Category text box and observe the list of categories.

All the categories are visible under Search Category under Service Request.

171298

The Priority Matrix did not display the correct values for Problem Management module

Steps:

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

2. Select Settings > Design Studio.

3. Navigate to Modules > Problem > Configurations > Problem Matrices > Priority Matrix. The Problem Matrix list page is displayed.

4. Click New and then select Tenant.

5. Click Save.

The Priority Matrix displays the correct values for Problem Management module.

171879

On Manage Release Records list page, Advanced Filters were applied but not reflected on the list page.

Steps:

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

2. Select Service Management application.

3. Navigate to Release > Manage Release Requests.

   The Manage Release Requests List page is displayed.

4. Select the  Filters icon. Within the filters panel, select the Advance Filter icon.

   The Advance Filter pop-up window is displayed.  

5. Click Add Filter Set. Add the Field, Operator, and Value. Click Apply.

6. Verify that the list on the Manage Release Request list page is updated based on the applied filters.

The Manage Release Requests list now displays results based on the applied Advanced Filters.

172560

A date-based filter was not executed successfully in the API Explorer under the Retrieve a Record (GET) section.

Steps:

1. Log in to the application as an Analyst.

2. Select the Settings icon from the top panel.

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

   The Explorer page is displayed.

4. Navigate to Retrieve a Record (GET) section.

5. Enter all required details under General section.

6. Click Add Filters. The Condition Builder pop-up window is displayed.

7. Select Field as Join Date, Operator as Between, and specify the Value.

8. Verify that the query runs successfully and returns the expected results.  

The API Explorer now successfully executes date-based filters in the Retrieve a Record (GET) section.

170925

While configuring the Priority Matrix, the Urgency, Impact, and Priority fields displayed incorrect data due to incorrect Datasource mapping in the Form Designer.

Steps:

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

2. Navigate to Module > Service Request > Form Designer.

   The Form Designer list page is displayed.

3. In the list, search for Priority Matrix form.

4. Click the Priority Matrix ID hyperlink. Navigate to Design Form tab and click Settings icon for the Urgency field.

   The Urgency pop-up window appears.

5. Navigate to Datasource tab and verify the mapping for Urgency. It should be mapped only to the Service Request (SR) Module.

6. Note: Repeat the same verification for the Impact and Priority fields.

Note:

Repeat the same verification for the Impact and Priority fields.

The Form Designer maps the Urgency, Impact, and Priority fields to the SR module, and the values are displayed correctly in the Priority Matrix.

169395

Deactivated Workgroup names are not displayed on the Analyst(s) configuration page as part of the resolution. 

162774 

Incorrect records were fetched for a given date range in Manage Change Record List page. 

Manage Change Record List page displays all the relevant data for the mentioned date range successfully.  

171864 

The Publish To stepper in the Role Mapping workflow did not display values for User Category and Grade. 

172932 

The e-mail notifications triggered through Workflows displays accurate data successfully. 

171933 

New Change Records on the Manage Change Record List page were not displayed. 

Manage Change Record List page displays all the New Change Records successfully as part of the resolution. 

170926

When an incident was in the Resolved state, the Please link the article that helped field in the Solution tab displayed no records, even though published Knowledge Base (KB) articles were available.

Steps:

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

2. Navigate to Incident > Manage Incidents. The Manage Incident – List page is displayed.
   

3. Click Incident ID hyperlink for the incident with the status Resolved.
   

4. Verify the Please link the article that helped field.

Published Knowledge Base (KB) articles are displayed in the Please link the article that helped field for incidents in the Resolved status without any issue.

172799

A discrepancy in timestamps was observed when comments were added to tickets. The timestamps did not consistently reflect the actual time the comments were entered. 

Steps:

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

2. Navigate to Incident > New Incident for User. 
   The New Incident For User page is displayed. 

3. Enter the required details and click Submit. 

4. Navigate to Incident List page and open the newly created incident.  

5. Click COMMUNICATION tab and enter a comment. 

6. Next, Log in as an Admin. 

7. Navigate to API Hub > Explorer. 

8. The Authentication (POST) page is displayed. 

9. Enter the API URL to access the User and incident record details.  

10. Verify the updated timestamp  of the incident record.

Timestamps now consistently reflect the actual time when comments are added to tickets.

171515

The API payload was unable to generate any results.

Steps:

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

2. Navigate to API Hub > Explorer.
   The Authentication (POST) page is displayed.

3. Enter the required details and click Send.

The API payload is generating results as expected.

171425

An error message was displayed when identical child values were mapped to different parent master values in the Common Master.

Steps:

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

2. Navigate to Platform Masters > Common Master.
   The Common Masters page is displayed.

3. Create Master Type (Parent) with two distinct Master Values (example; Value1, Value2).

4. Create Master Type (Child) and establish a parent-child relationship with Master Type.

You can map identical Child Values to different Parent Master values in the Common Masters without any errors.

172432

The API response returned the Activities field as empty when retrieving the Approval/Reject remarks from the application.

Steps:

1. Double-click Postman icon to open the application.

2. Enter the API URL in the POST text field and request in the request placeholder.

3. Click Send and verify the Activities field value.

The Activities field values are displayed without any issue.

172841

Applicable to the Catalog Microsoft Sentinel SIEM Access for which Work Orders were not generated.

Steps:

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

2. Create Service Request using Catalog Microsoft Sentinel SIEM Access with a specific Workgroup.
   

3. On SR Approval from Reporting Manager verify the dropdown value selected during SR creation.
   

4. Based on the defined condition verify if the workorder is logged.
   

5. When the Work Order is resolved then the Parent SR is resolved.

Work Orders are generated using Catalog Microsoft Sentinel SIEM Access.

173100

Work Orders were not generated when the users created an SR using the Catalog Public Cloud Service Control Policy.

After the approver selected a value in the Approver Group dropdown and while approving the SR after submitting, the values were not saved and workorders were not generated.

Steps:

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

2. Create an SR using the Catalog Public Cloud Service Control Policy.
   

3. Select value in Approver Group dropdown.
   

4. Submit the values and observe if the values are saved and Work Order is generated.

Work Orders are generated when users created an SR using the Catalog Public Cloud Service Control Policy.

173276

Users were not able to create Incidents on behalf of the other users, though the users were registered.

Steps:

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

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

3. Click New to create an Incident.
   

4. In the Requestor field select the user to create an Incident on behalf.
   

5. Observe if the user is displayed in the dropdown.

Users can create Incidents on behalf of the other users.