Release Notes v6.1.0.1 HF07

• Process oriented mechanism when adding new extensions.
  
  
• Flexibility in managing extensions.

• This improvement adds customization while designing forms by enabling selective file type extensions.
  
  
• Flawless execution amongst other applications such as parser that manages tickets with email.

Business Rule is created as, when an external requestor is updating the Ticket then the Analyst/Workgroup Analyst should get the notification. But in this scenario the following occurred.

Scenario 1: When an Analyst updated the ticket then the notification was triggered. 

Scenario2: BR was failing. 

Steps: 

1. Log in to Apex application as an Application Designer.
   
   
2. Create a Business Rule with below conditions and Actions.
   
   Based On Condition:
   Field: Updated by
   Operator: is Not  
   Value: Analyst(s) of Tenant
   
   Actions
   Notify Recipients
   Notify Analyst
   Select Template
   Medium: Email
   To: Analyst
   
   
3. Update any Incident as an External User apart from the configured user.
   
   
4. Verify if the mails are triggered or not. 

Prerequisites: 

1. Configure Approver 1 and Approver 2. 
2. Configure a Workflow with Refer Back configuration. 
3. Create Refer Back status in the Form Designer. 

Steps: 

1. Log in to the Apex application as an End User. 
2. Navigate to Incident > My Incidents. 
3. Click New to create a new Incident.  
4. Enter the required details and click Save. 
5. Log in to the Apex application as an Approver 1. 
6. Provide the required details and send to Approver 2.
7. Log in to the Apex application as an Approver 2.
8. Review the details and Refer Back the Incident to Approver 1.

1. Log in to the Apex application as an Analyst.  
2. Navigate to Change > Change Request > Manage Change Requests. 
3. On Manage Change Request List page, select Advance Filter) icon.  
4. Click Add Filter Set to add more filter conditions. 
5. Select the Field as Created-on, set the Operator to Between. 
6. Click the  calendar icon to choose the start and end dates under Value. 
7. Enter the date range in the format (e.g., October/01/2024 - October/14/2024).  

Steps: 

1. As an End User raise the ticket by sending an email to the support team.
   
   
2. Mention the support Email ID in the CC field of the email. 

Steps: 

1. Log in to the Apex application.
   
   
2. Select Service Management application.
   
   
3. Click the Settings gear and select Platform Studio.
   
   
4. Navigate to Access Control Center > User.
   
   
5. Select the required Domain and Sub Domain from the drop-down.
   
   
6. Search for a username in the Search bar on User List page and then select the next page.
   
   
7. Check and verify if the filter gets reset. 

The Response SLA was considered for weekends, and the wrong deadline was displayed even though weekends were not selected in the Service Window configuration.

Steps: 

1. Log in to the Apex application as Application Designer.
   
   
2. Select Service Management application.
    
3. Click the Settings gear icon and select Design Studio.
   
   
4. Select the Application option from the left selection panel. Scroll down and click SLA Designer > Service Window.
   
   
5. Select the required Domain and Sub Domain from the drop-down.
   
   
6. Provide all the required details in General tab.
   
   
7. In the Service Window tab, select the Service Window Type as General and select the check box(s) of the days for which you wish to keep the window active.
   (For weekdays, select days from Monday to Friday) 

The Response SLA consideration is done accurately for the days defined in Service Window. 

Steps:

1. Log in to the Apex application.
   
   
2. Navigate to Incident > Manage Incidents.
   
   
3. Click Incident ID hyperlink.
   
   
4. Verify that the Workaround SLA value in the Incident detail page and Incident list page is same

Steps: 

1. Log in to the Apex application as an Analyst.
   
   
2. Create an Incident through mail.
   
   
3. Navigate to Incident > Manage Incidents.
   
   
4. Click the Incident ID hyperlink and check the Description (where body of email has been mapped). 

The breadcrumb menu, which displays the navigation trail of the previous sections, was not displayed.  

Steps: 

1. Navigate to Incident > Manage Incidents.
   
   
2. Click New to create a new incident.
   
   
3. Observe the navigation panel.  

In the change management workflow, for role-based approval, admin was unable to select the secondary owner for the workgroup.  

Steps: 

1. Navigate to Service Management > Module. Select Change.
   
   
2. Click Workflow Designer.
   
   
3. Open a workflow, select the Design Workflow step.
   
   
4. On the Design Workflow, select User Approval > Configure Properties.
   
   
5. Select Approval Type as Role Based Approval and configure with the field as 'Workgroup'.
   
   
6. Add the Primary and Secondary Approvers.  

In the change management workflow for role-based approval, the admin can select the secondary owner for the workgroup.

.eml and .msg attachments were not attached to the tickets created through email to ticket functionality.

Steps: 

1. Log in to the Apex application.
   
   
2. Navigate to Design Studio > Application > Notification Parser.
   
   
3. Select New and configure Parser for Create Record with System Defined Key as an Attachment.
   
   
4. Validate by sending email to the mailbox which is configured with the above parser. 

The minimum height configuration was not working as expected for Long Text control in the Form Designer.

Steps: 

1. Log in to the Apex application.
   
   
2. Navigate to Designers > Form Designer.
   
   
3. Configure Long Text control on the form.
   
   
4. Verify on the record.

Steps:

1. Navigate to Design Studio > Form Designer > Form Controls.
   
   
2. Configure the Long Text control with Rich Text editor.
   
   
3. Observe the above configured Long Text field.  

1. Log in to the Apex application as an Analyst.
   
   
2. Navigate to Incident module and open any form of Form Type as Transaction Form such as Manage Incident form.
    
3. Specify value for the Efforts field.
   
   
4. Observe Change History.

Prerequisite:  

1. Navigate to Admin form (Which contains Sort Order) configuration page by putting form under Maintenance > Select Render as Fields as Sort Order. 

 Steps:  

1. Log in to the Apex application. 

2. Navigate to Problem > Manage Problem Records > Click Configurations.  

3. Select a form which contains sort order. For e.g., Impact, Urgency, Priority and Risk. 

4. Click New > Enter all the mandatory details. 

5. Enter the Sort Order (1) > select the Active checkbox > click Save. 

6. Again, click New > Enter all the mandatory details. 

7. Enter different Sort Order (9) > Select the Active checkbox > click Save. 

Prerequisite:

1. Module must be Change. 
2. User must be part of Groups > Record Attributes Groups. 

Steps:

1. Log in to the Apex application as an Application Designer.
   
   
2. Click Groups drop-down.
   
   
3. Select the groups.
   
   
4. Click pagination and see if next page is displayed.

When the Filter condition Analyst is Empty was saved on the Manage Incident list page, it still displayed all the Incident records.  

Prerequisite: 

On the Manage Incidents list page, create and save a default view.  

Steps: 

1. Navigate to Service Management > Incident Management. The Manage Incident list page is displayed.
   
   
2. Verify the list of Incidents as per the default view.
   
   
3. Refresh the page and verify the list of Incidents as per the default view. 

The Incident records are displayed as the saved default view.  

Prerequisite:

The Landing page should be set as a consumer end page in the User Profile. 

Steps:

1. Log in to the Apex application as an Analyst.
   
   
2. Navigate to logged-in User Profile.
   
   
3. Click Switch User.
   
   
4. Select a Role from the drop-down menu.
   
   
5. An error message is displayed. 

Prerequisite:

Configure the Business Rule Designer with the required conditions. 

Steps:

1. Log in to the Apex application as an Analyst. 
2. Navigate to Service Management > Request > Manage Service Requests. The Manage Service Requests list page is displayed. 
3. Click New. 
4. Create a new Service Request record with the matching BRD conditions. 
5. Log in to the Apex application as an Application Designer.  
6. Navigate to Design Studio > Module > Business Rule Designer. The Business Rule Designer list page is displayed. 
7. Verify the Record Impacted. An error message is displayed. 

158267

Steps: 

1. Log in to the Apex application as an Analyst.
2. Navigate to Incident > Manage Incidents.  

N/A

Service Request fields display blank data during the update of ticket and do not update further until the form is refreshed.

Steps: 

1. Log in to the Apex application as an Analyst.
   
   
2. Select Service Management application.
   
   
3. Navigate to Service Request > Manage Service Requests.
   
   
4. Click the required SR ID hyperlink to view the details page.
   
   
5. Verify the data displayed in fields under Catalog Details. 

N/A

The column width adjustment made in the Incident list page by dragging the separator does not persist after navigating to an Incident detail page and reverting to the list page.

Steps:

1. Log in to the Apex application.
   
   
2. Navigate to Incidents > My Incidents.
   
   Note: Navigate to any list page of Incident Management module.
   
   
3. Drag and drop the columns in the list page to re-arrange.

N/A

Steps: 

1. Log in to the Apex application as an Application Designer.
   
   
2. Navigate to Design Studio > Module > Workflow Designer.
   
   
3. Click New.
     
4. Navigate to Set Trigger & Conditions.
   
   
5. Choose Category/Change Category fields which is of Control Type = Tree View.
   
   
6. Choose the Operator and Value.
   
   
7. Configure and Save the Workflow.
   
   
8. Navigate to Set Trigger & Conditions step and verify whether the values are displayed for Category/Change Category fields.

Prerequisites:  

1. Navigate to Design Studio > Module > Groups > Dynamic Groups.
   
   
2. Click the Groups dropdown and click Add Group.
   
   
3. Create a Record Attribute Group and add Users to the group. 

 Steps: 

1. Log in to the Apex application as an Application Designer.  
   
   
2. Navigate to Design Studio > Module > Scheduler.
   
   
3. Click New.
   
   
4. Enter all the mandatory details.
   
   
5. Navigate to Actions > Notify Recipients.
   
   
6. Navigate to Recipients > To.
   
   
7. Select Recipient as Record Attribute Group and select a group name.  

N/A

158184

Users are unable to upload values for child fields in the import template.

Steps: 

1.  Log in to the Apex application.
   
   
2. Create a field with a parent value in the common master, and another field as the child value of the parent field.
   
   
3. Download the template and add the parent and child values according to the dropdown options.
   
   
4. Validate by uploading, an error will occur.

 N/A

1. Navigate to Incident > Manage Incident details page.
   
   
2. Click Incident ID hyperlink.
   
   
3. Observe the Long Text field.  

N/A

1. Log in to the Apex application as an Analyst.
   
   
2. Navigate to Change > Manage Change Record. Manage Change Record list page is displayed.
   
   
3. Click New > select Tenant.
   
   
4. Enter Characters 51576 in the Symptom and Description field and Risk field.
   
   
5. Enter all the mandatory fields > click Save.
   
   
6. Navigate to Manage Change Record list page.
   
   
7. Click ID hyperlink of the Change Record created above to view the CR details page.
   
   
8. Click Change History > Communication tab.
   
   
9. Expand any sent email. Click Read more. Verify the displayed values.

Steps: 

1. Log in to the Apex application.  
2. Navigate to Service Request > My Company Service Requests. The My Company Service Requests List page is displayed.  
3. Click any SR ID hyperlink.