Release Notes v6.1.0.1 HF06
  • 07 Oct 2024
  • 6 Minutes to read
  • PDF

Release Notes v6.1.0.1 HF06

  • PDF

Article summary

New Features

Following enhancement introduced in this v6.1.0.1 HF06 release.

Improvement NameImprovement DescriptionBenefits
SLA Restart Feature when the SLA is in Active or Completed state.

User Persona: Application Designer
This enhanced feature allows to Restart an SLA for the defined condition in the Filter Set based on its Active or Completed state.

For more information, refer to SLA Restart.
  • Restart SLA independent of its state such either Active or Completed along with option to select both.
  • User friendly approach to manage SLA.

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

Known Issues

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

Issue IDIssue DescriptionWorkaround

157172

Refer back option is not available in the Workflow to refer back a record.

N/A

157411

Scheduler was configured to notify the escalation to the selected Record Attribute Groups. Based on the condition match, it should trigger to the specific user of the selected group.

Prerequisites:

  1. Configure Record Attribute Group with a Group Name.

  2. Based on the Parameters, add the users.

Steps:

  1. Log in to the Apex application as an Application Designer.
     
  2. Navigate to Design Studio > Designers > Scheduler.
     
  3. In the Actions, select Notify Recipients.

  4. Select Record Attribute Group and then, select Group Name that was created earlier as its value

N/A

155464

Text files with extension .txt are not getting attached to the tickets.  


You can attach files with 33 extensions to the tickets. The allowed extensions of these 33 file types are: .3gp,.m4v/MP4,.docx,.png,.html,.pdf,.ppt,.mp3,.ogg,.eml,.ogv,.odt,.wav,.mp4/M4V,.m4a,.pptx,.xlsx,.msg, .jpeg,.zip,.xls,.pps,.gif,.doc,.wmv,.ppsx,.txt,.avi,.mpg,.jpg,.webp,.json, and .sql 

154734The attachments with .eml and .msg extensions are unavailable in the tickets created through email-to-ticket functionality.N/A
157384Mandatory field’s data was not getting displayed.  

N/A


157501

In the Change Management (CM) module, while users can select the Primary Owner, they cannot select the Secondary Owner.  Secondary Owner is a multiselect control which is currently not supported.

 

157501 During workflow configuration, users can select the Primary Owner of the workgroup as approver, however, system does not currently support the selection of a Secondary Owner as an approver. The Secondary Owner workgroup option is a multi-selection control, which is not supported currently. 


N/A

Fixed Issues

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

Issue IDIssue DescriptionScenarioResolution
157422In the Change Management module, certain records requiring approval from at least one approver, as per the configured Workflow, were still displaying a "Pending for Approval" status even after one approver has approved it. Prerequisites:
  • Configure more than one approver in the Workflow – User Approval component.

  • Approval condition should be that any one member should approve.

Steps:

  1. Log in to Apex application.

  2. Navigate to Change > Manage Change Requests.

    Or
    Navigate to Change > My Change Requests.

  3. Click the Change Record ID that is pending approval.
In the Change Management module, records requiring approval from at least one approver, as per the configured Workflow, show status as ‘Approved’ after being approved by at least one approver. After approval from one approver, the status for other approvers is displayed as Approval Not Required.
157734The configured role was not mapping to the user.

Steps:

  1. Log in to Apex Application as a Super Admin.
     
  2. Navigate to Platform Studio > Access Control Center> Role Mapping.
     
  3. Select New.
     
  4. Validate by publishing the role mapping.
Note
This is applicable for User Role Mapping at Application level as well. To validate the above steps, navigate to Design Studio > Application > Access Control Center > User Role Mapping.
Configured Role is mapping correctly to the user.
156437
Reminders for both new and old records are sent multiple times to notify the recipients. 

Steps:

  1.  Navigate to Module > Incident Module > Scheduler.
  2. Enter all the desired details for General and Frequency Step. 
  3. Navigate to Condition step.
  4. Click Add Filter Set to add condition. Click Next.
  5. Under Actions step, click Notify Recipients tab.
  6. Toggle the Exclude already processed records button. 
Reminders are sent only for new records to notify the recipients. 
157954

Analysts were unable to link any incident or other records to an incident. 

Steps: 

  1. Navigate to Incident > Manage Incidents.

  2. Click New to create a new incident.

  3. On the New Incident details page, click the Links tab. Click the Link dropdown to link any incident or other records.  

The Link dropdown functions correctly, allowing to link incident- or other records to an incident. 

157477In the Change Management module, undo button was not working as expected in the Workflow configuration.Steps:
  1. Log in to Apex application.

  2. Navigate to Design Studio.

  3. Select Module > Change.

  4. Navigate to Designers > click Workflow Designer.

  5. Click New.

  6. Fill in all the details in the General step.

  7. Click Save > click Next.

  8. Select the trigger and condition in the Set Trigger & Conditions step.

  9. Click Save > click Next.

  10. In the Design Workflow step, drag and drop any component on to the canvas.

  11. Clickon the added component > click Delete.

  12. Click(undo) icon.
In the Change Management module, undo button is working as expected in the Workflow configuration.

156996The parent and child relationship was not working in the pre-production instance.

Steps:  

  1. Log in to Apex application as an Analyst.

  2. Navigate to Incident > Manage Incidents.
     
  3. Click New.

  4. Navigate to the General tab > Prioritization.

  5. The Serial Number field is added newly, and Data Source is Serial Number from the Fixed Asset form in Asset Management.

  6. The Asset Customer field is added newly, and the Data Source is the configured Customer from the Fixed Asset form in Asset Management.

  7. Navigate to General > Classification > Requestor.

  8. The Requestor field is linked to the Asset Customer as its parent value. All configured values will load based on the parent value chosen.  
Parent and child relationships are working in the pre-production instance.  
157155In the Service Request (SR), when a Work Order (WO) was created through the SR, not all fields were displayed correctly in the WO form. Additionally, the auto-linking did not occur for the new WO generated from the SR link.

Steps

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

  2. Navigate to Service Request > My Service Requests.

  3. In the Manage Service Requests List page, click SR ID hyperlink.

  4. Click the Links tab and click Create arrow to select Work Order option from the list. 
 When linking a Work Order (WO) to a Service Request (SR), all the fields in the Work Order form are displayed as expected.
157952The attached email was not getting parsed from the inbox and the remaining emails were not getting parsed.  

Steps:

The email with .msg attachments were not getting parsed as the content type was coming as ‘null’ for emails.  

The attached emails are getting parsed and .msg files are getting attached as .eml files.  
157753

Rich Text editor was not working as expected.  

Steps:

  1. Navigate to Service Management > Design Studio > Select the Module as Knowledge Management.
    The Manage Knowledge Record list page is displayed.

  2. Put the form under maintenance and add a Long Text control (Rich Text Editor) with validation as Field should be disabled when status changes to Awaiting Approval.

  3. Publish the form.

  4. Create a new record.

  5. Approve the created record and once the status is changed to Awaiting Approval, verify the long text field (Rich Text Editor).
Rich Text editor is working as expected.  
154161

Customer wanted a new feature in the Change Management (CM) module, so that data entered in PLANNED START TIME and PLANNED END TIME should not change and follow the below protocol.

  1. For Date or Time fields, no time zone conversion will be applied. Time zone conversion only applies to datetime attributes.

  2. Only the Date attribute will display the date without default time details, similar to Only Time attribute.

Steps:

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

  2. Select the module as Change > Designers > Form Designers > Add the Date and Time attributes.

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

  4. Create a Change Record with PLANNED START TIME and PLANNED END TIME in any time zone.

  5.  Log in to the Apex Application as an Analyst in a different time zone.

  6. Verify if the PLANNED START TIME and PLANNED END TIME are displayed in the same time zone as the one it was created in. 


 

The PLANNED START TIME and PLANNED END TIME are displaying as desired.
69387While importing user data from Azure AD, records with an empty User Name column value were also being stored in the user table. This was causing issues on specific pages while fetching user details.

Steps:  

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

  2. Navigate to Design Studio > Module > Scheduler.

  3. Navigate to the Actions stepper and click Call API action.

  4. Enter the mandatory values and go to Column Mapping.  
Mandatory value checking for User Name has been implemented for Azure AD Import.   




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.