Release Notes v6.1.0.1 HF07
  • 17 Oct 2024
  • 8 Minutes to read
  • PDF

Release Notes v6.1.0.1 HF07

  • PDF

Article summary

Improvements

Following improvement is introduced in this v6.1.0.1 HF07 release.

Improvement NameImprovement DescriptionBenefits
Configure Attachment Properties in Global Settings

User Persona: Super Admin
Add new extensions in the Global Settings on the Platform with CR Approval.

For more information, refer to Attachment Properties.
  • Process oriented mechanism when adding new extensions.

  • Flexibility in managing extensions.
Configure File Extension Properties



User Persona: Application Designer
Configure File extension properties on File Upload control that allow you to select required File Type extensions on the Forms.

For more information, refer to File Upload -Form Designer.
  • 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.
Designer Execution Sequence

User Persona: Application Designer
Configure the executing order of Business Rule, Workflow and SLA while publishing a form.

For more information, refer to Publish document in Form Designer.
Flexibility to publish a form with required execution order for Business Rule, Workflow and SLA.

Note
For more information on prerequisites of Apex v6.1.0.1 HF07, refer this link.

Fixed Issues

The following section provides details of fixed issues in Apex v6.1.0.1 HF07:

Issue IDIssue DescriptionScenarioResolution
157172When approver referred an incident back, the Incident status did not change to Refer Back as expected.

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.
When an Approver, Refers Back an Incident, the status of the Incident is successfully changed to Refer Back.
158381Incorrect records were displayed on the list page of Manage Change Requests for a specified date range when selected in the Advanced Filter.

Note: 

The issue is same for the Lis pages of Manage Incidents, Service Requests, Knowledge Records, and Problem Records.


Steps:
  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).  
Correct records are displayed on the list page of Manage Change Request for a specified date range when selected in the Advanced Filter. 
157856 Even though Include In Template button was disabled, the downloaded CMDB template from Infrastructure as a CI still retrieved data from deleted fields. 

Prerequisites:  

  1. Log in to the Apex application as an App Designer.  
  2. In the Form Designer:  
    1. In the Design List View step, configure the Import action. 
    2. In the Designer Form step, enable the option Include In Template for mandatory fields.  

Steps:  

  1. Log in to the Apex application as an Analyst 
  2. Navigate to CMDB > Infrastructure as CI.  
  3. Click Import icon and select Upload File 
  4. Select the required fields and click Download. 
The downloaded CMDB template from Infrastructure as a CI contains only the configured fields.   
158641Emails were not processed to tickets due to an in-correct email address.

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. 
The invalid Email IDs entered in CC/TO/BCC fields are skipped and the ticket gets created successfully after the resolution.
157400The filter got reset when navigated to next page while searching for a user under User List page in Platform Studio.

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 filter does not get reset when navigated to next page while searching for a user under User List page in Platform Studio.
158752  

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

157421There was a mismatch in the Workaround SLA value in the Incident detail page and Incident list page.

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
The Workaround SLA value in the Incident detail page and Incident list page is same.


158196 
Some images in Incident were not displayed properly. If there were two images in the email body, one displayed correctly while the other did not.  

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). 
Multiple Images are displayed properly in the email body.  
156831

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.  
The breadcrumb menu displays the navigation trail of the previous sections.  
157501

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.

154734

.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. 
.eml and .msg attachments are attached to the tickets created through email to ticket functionality.

157671  

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.
The minimum height configuration is working as expected for Long Text control in the Form Designer.
155215Mandatory validation messages were not appearing for Rich Text Editor field, whenever the validation condition was met.

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.  
Mandatory validation messages are appearing for Rich Text Editor field, whenever the validation condition is met.
158262The Data Type for Effort field was displaying older values.Steps:
  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.
The Data Type for Effort field is displaying values as expected.
157392 
The Impact, Urgency, Priority and Risk values were being displayed in alphabetical order instead of being displayed according to the sort order specified during their creation. 

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

 


The Impact, Urgency, Priority and Risk values are being displayed according to the sort order specified during creation.
156565 
In the Change Management module, Role Based Approval using Dot Walking was not working. A multi-select dropdown had been configured to list various workgroups. Based on the selected workgroup(s), the primary owners should automatically be assigned as approvers in the workflow  

Steps 
 

1. Navigate to Design Studio > Select the Module > Workflow Designer 
 

2. Click the Workflow ID which is created in Workflow Designer page. 
 

3. Navigate to Design Workflow step. 
 

4. Double click on User Approval component. 

5. Approval Options select Approval Type as Role Based Approval.
 
6. Under Select Approval Role (Dot Walking) select “Additional Workgroup Approver.Primary Owner. 

 


Role Based Approval using Dot Walking is working as desired.  

Known Issues

The following section provides details of known issues and workarounds in Apex v6.1.0.1 HF07:

Issue IDIssue DescriptionScenarioWorkaround


158267


The configured View Filter functioned properly on the Incident List page until a refresh occurred. After refreshing, the filter disappeared, and only the Save as New View and Save Changes options are visible.

Steps

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

N/A

157794 The downloaded CMDB template from Infrastructure as a CI does not successfully import unique values. 

Steps:

  1. Log in to the Apex application.  
  2. Navigate to CMDB Infrastructure as CI 
  3. Click Import icon and select Upload File 
  4. Select the required fields and click Download. 
  5. Download the CMDB template and add unique values under the Serial Number column in the template.  
  6. Click Next and upload the downloaded CMDB template. 
N/A
158385  



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

156854

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

158316Change Category is not reflected in Set Trigger & Conditions under Workflow.  

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.
N/A
157411The Scheduler configured to notify escalation to the record attribute group is not triggering the notification.

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

158186The Long Text field is not getting displayed in expandable and scrollable format.Prerequisite:
Incident Status must be Closed.

Steps:
  1. Navigate to Incident > Manage Incident details page.

  2. Click Incident ID hyperlink.

  3. Observe the Long Text field.  

N/A

158615   Category field was unavailable to filter for both Incident Management (IM) and Service Request (SRlist page.  

Steps 
 

1. Log in to the Apex application. 
 

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


3. Click icon to add Filters and search for Category in the search bar. 


 


N/A



Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
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.