Currently we supported a threshold of 20% of maximum exceptions on entitlements. This means that within the person scope of the condition at maximum of 20% could be seen as exception and not having the entitlement to be visible as report entry. We made this configurable between 20% and 0%. This means we are more flexibel within the report because a group exclude could now be included as an report entry because the whole group is smaller than 20% of the organization especially higher level scopes like two division where one is really big an the other is really small. Another big advantage is that we can set this percentage on 0% which makes it much easier to create rules for a first setup.

We implemented an improvement where the requestGUID will be included in the Elastic audit logging document for custom audit messages. This will make it possible to establish a clear relationship between a product request and its corresponding audit messages, improving traceability.

With this change, there will also be a clear distinction between custom audit messages related to a product request and those related to a Delegated Form submission. This will help ensure better filtering, reporting, and overall insight into audit data.

We already support permission selection in the preview of grant & revoke permissions. But now we support the cached values from a target snapshot the same as in business rules entitlement selection. It's possible to refresh the cached entitlement using the button in this screen. Also the displayname of the permission is available in preview when using actionContext.PermissionDisplayName variable (This was previously only available when running in production).

Starting with this release, product request deletions are included in audit logs (Elastic). This prevents gaps in the audit trail when user accounts and related product requests are automatically removed. The full product request lifecycle is now traceable for compliance and investigation purposes.

A new overview shows all in all target systems, the business rules where each entitlement is configured, and the persons who currently have the entitlement. This helps you quickly find and replace entitlements, remove them from business rules, and answer audit questions about when an entitlement is granted.

The overview also indicates whether an entitlement still exists in the target system. If entitlements are still referenced in business rules but no longer exist in the target system, a warning badge is shown.

The overview can be found under .

is now available on a separate tab (the button has been replaced).

Business rules can now be created directly from rule mining report entries, making it easier to build the most efficient set of business rules based on existing entitlements in a target system.

When creating a business rule from an entry in a rule mining report you can set its name, categorize the rule, select the entitlements the rule must assign, and choose a condition (if multiple conditions can identify the same group of people).

: Rule mining is a beta feature included in the Governance module. It is available upon request.