Who is this article for?

  Administrators interested in learning more about solution updates.

  No special access or permissions are required.

This article outlines the product changes, enhancements, and fixes that have been implemented in the v1.4 release, available from 11 September 2024.

1. Features

This release introduces custom fields functionality, licensing, and improving user control over configuration, record management, and data entry.

1.1. Custom field management

• Configuration Register - Users can now manage custom fields through a new configuration register.  Teams have access to create, edit, activate, archive, or delete custom fields with various data types (short text, long text with formatting, numerical, date and time, list – single select and multiselect).
• Record integration - Custom fields can now be integrated and managed across multiple records and entities, including Actions, Risks, Incidents, and more. Users can update and apply custom fields to subtypes and objects within the system.
• Visibility and permissions - Controls are in place to restrict field creation, editing, and viewing based on user roles, ensuring only authorised users can make changes.

1.2. Licensing

• API Endpoint restrictions - Business Users are now restricted to accessing only specific endpoints related to Actions and Incidents, preventing unauthorised data access.
• License-based UI restrictions - The UI dynamically hides elements and pages based on the user’s license type, ensuring they only see relevant features and reducing the risk of unauthorised access.

1.3. Principal Risks

• Simplified Principal Risks - Principal Risks was built to a high specification, but in this release, it was simplified following customer feedback by removing unnecessary elements like child items and team assignments, making this easier to manage.

1.4. UI/UX enhancements

• New icons - Updated icons for key objects (Risks and Tests) for better visual clarity.

1.5. Technical enhancements

• MySQL Outbox archiver – A new background job has been implemented to archive outdated messages in MySQL, ensuring optimal performance.