Updated: Apr 1
We are pleased to announce that Ruleguard version 4.11.0 is now live!
This update contains the following changes:
Add the ability to indicate that a ‘Transition’ between two ‘Issue stages’ is subject to a Service Level Agreement (SLA) expressed in days.
Transitions that breach the SLA display a record on the Issue card and these breaches can also be queried and saved as Pins within the Issues grid.
General Improvements and Fixes
Refined the alphanumeric sort order of SMF designations within a Responsibility Map for a clearer presentation.
Made a minor visual change on the Issue Card to indicate where comments exist for an Issue. (V4 experience only).
Made a minor UX improvement to rename tiered selection lists to ‘Selection (Tiered) to be consistent with other Field types.
Added ‘Account Name’ to Sailpoint file extracts for group enterprise clients with multiple Ruleguard accounts.
Resolved an issue where heading names containing commas on grids (e.g., the Issues grid) were causing CSV downloads to read these as separate columns (i.e. as delimited).
Resolved an issue whereby Shared Topic notifications were reasserting / looping updates were due to be accepted when they had already been.
Resolved an issue whereby ‘layering’ (stacking) Issues permissions was not granting additional access intended.
Resolved an internally captured bug where Field values were not always being cleared in Archived Fields in certain use-cases involving ‘visibility rules.’
Resolved an internally raised bug whereby removing an Issue ‘type' permission only was not removing dependent permissions unless removed in a specific sequence (still displayed)
v4 User Experience rollout of 01 Feb 2023
In a Rush?
Don't always have time to read our blog posts right away? You can always access our release notes later by clicking the release version in the Ruleguard Welcome menu.
If you encounter any problems or have any questions about this update, please let us know at email@example.com or contact your Delivery Manager.