Release Notes v6.1.0.1

🎯 Now Live!
Release Date | 4^th July 2024

New Features

The following section provides key highlights and module-wise description of new features introduced in Apex release.

Note

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

Let's take a quick look at our Platform Studio user persona.

The following section provides a sneak-peak of the functionalities added for Platform Studio.

Let's take a quick look at our Design Studio user personas.

The following section provides a sneak-peak of the functionalities added for Design Studio.

The following section provides key highlights and Application-wise description of new features introduced in Apex Release.

Let's take a quick look at our Service Management user personas.

The following section provides a sneak-peak of the functionalities added for Service Management.

Let's take a quick look at our Asset Management user personas.

The following section provides a sneak-peak of the functionalities added for Asset Management.

Note

Localization functionality is not available in Release v6.1.0.1.

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

Issue ID	Issue Description	Workaround
152617	List Page Column-Level Filter Freezes When opening the column-level filter on the List page, the page may freeze if the data source for that column has more than 2,000 records. For example, applying the filter to the 'Requestor' field, which maps to the User Master with 10,000 records, can cause this issue. The Requestor field in the filter section takes lots of time to load. An error message is displayed indicating "Page Unresponsive".	Use the Basic or Advanced Filter options on the List page instead of the column-level filter to avoid the page freeze.
64158	While saving the 3rd SMTP configuration, an error message "An Error Occurred" is displayed.	N/A
152838	Form fields referencing a Tree control are not supported in the Tile view control.	Until a fix or enhancement is provided, users should avoid using tree-referenced form fields in the tile view control. Alternatively, implement a plain text field within the form, ensure the plain text field is programmatically updated to reflect changes from the tree view control then use this plain text field in the tile view control to display the necessary information.