Crescendo 6.3.1.1 Patch 4

174035

Users were experiencing issue while configuring SLA Value and an error message was displayed as “An error occurred while processing your request”.

Steps:

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

2. Configure the Common Master as SLA Offerings.
   

3. Utilize SLA Offerings in Contract Management as a Single Choice field.
   

4. On the IM Details page, create an SLA Offering field (Single Choice) and configured the data source as the Contract Management table with SLA Offerings as the source.
   

5. Configure an SLA Rule named Contract Communication SLA, using Priority and SLA Offering as the SLA Criteria.
   

6. When attempting to add an SLA Value, the SLA Offering field is displaying unrelated options such as Time Zone, Country, along with the expected Common Master values.
   

7. Due to this, not able to proceed with configuring the SLA Value. An error is displayed as “An error occurred while processing your request”.

Users are able to configure SLA Value from the defined SLA Rule successfully.

174441

After submitting the form with the selected Criteria and Values, both the Priority and SLA Offerings fields appeared blank upon returning to the list page.

Furthermore, opening the entry displayed that the criteria have been duplicated.

Steps:

1. Log in to the application as an Analyst.
   

2. Select Service Management.  
   

3. Navigate to SLA Designer > SLA Value. The SLA Value Details page is displayed.
   

4. Specify the Criteria and Value fields.
   

5. Navigate to SLA Value List page and observe the Priority and SLA Offerings fields.

After submitting the form with the selected criteria and values, both the Priority and SLA Offering displays the values. fields appear blank upon returning to the list page.

173861

The Requestor and Tenant fields were not displaying any values.

Steps:

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

2. Navigate to Change > Manage Change Record. The Manage Change Record List page is displayed.

3. Click New to create a new CR.

4. Open the newly created CR.

Observe the Requestor and Tenant values.

The Requestor and Tenant fields are displaying the values.

174304

The Tree View configurations were not saved when the Save button is clicked.

No response is seen when the Cancel button was clicked.

Steps:

1. Log in to Apex as an Application Designer.

2. Navigate to Module > Incidents > Form Designer.

3. The Form Designer List page is displayed.

4. Search for the Manage Incidents form and click its ID hyper link.

5. Change the status of the Manage Incidents form from Published to Maintenance.

6. Navigate to the Design Form step.

7. Under Form Controls, drag and drop the Tree View widget onto the designer canvas.

8. Click the Settings icons on the Tree View control and open the Properties tab.

9. Set Render As to Selection Tree.

10. Select the Data Source tab and set the following:

    1. Data Source: Table

    2. Layer: Service Management

    3. Module: Incident

11. Choose Values for the Table and Label Column fields.

12. Click Save and verify that the Tree View configurations are saved.

The Tree View configurations are saved, and the Save and Cancel buttons are working as expected.

174034

When an Incident was raised through the Email to Ticket functionality with the subject line 'Potential Phish', the ticket was not created. Instead, the email was moved to the Archive folder.

Prerequisites:

1. Mailbox should be configured.

2. Notification Parser should be configured.

3. Job should run.

Steps:

1. Send an email to the mailbox ID with email subject line Potential Phish.

2. Log in to Apex as an Analyst.

3. Navigate to Incident > Manage Incidents.

   The Manage Incidents List page is displayed.

4. On the Manage Incidents list page, verify whether the ticket is created or not.

Tickets from Email to Ticket functionality are successfully getting created through emails.