• System icons are not correctly shown when you’ve created an new rule mining report and the new one fails to create and the previous rule mining report is shown.
• Active Directory account isn’t removed when an Exchange mailbox creation fails on the create account action of an Built-in Active Directory target system. This results in an unmanaged Active Directory account. We fixed this so the created Active Directory is deleted on rollback when Exchange fails.

Service Automation

• PowerShell 7 support for local Service Automation Agent

• No agent pool selection results in a random pool selection instead of default pool
• Delegated form tasks stay in running state
• Search results in ordered dropdown isn’t ordered anymore

We have released a hotfix to resolve an issue that prevented images from being uploaded on the Company Settings page. Uploading an image resulted in a 400 Bad Request error. The issue has been identified and resolved, and image uploads are now working as expected.

We’ve released a hotfix to address an issue affecting Automation Variables used in the new Product Actions, PowerShell data sources, and Delegated Form tasks. In some cases, newly created Automation Variables and recent updates to existing variable values were not reflected during execution, causing scripts to continue using previous values. Scheduled Automation Tasks were not affected. This issue has now been resolved.

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).

• Can not save a Dynamic Form using a form component with ‘depencancy on URL query parameter’
• Can not save or edit a Self Service Product resource owner if the old resource owner group is deleted from HelloID

• It wasn’t possible to add new tags to an incident webhook or email to limited when an webhook or email is triggered

• Rule mining report shows no results for system when person.accounts fields are used for correlation and the fieldname & value exists for multiple target systems.
• Rule mining report shows no results for system when person.accounts fields are used for correlation and PascalCasing is used in the field name.
• SMTP with capital letters is not used as primary for Active Directory with Exchange integration enabled. The first value in array was used as primary instead of the value with capital SMTP.
• The same subpermission reference in an entitlement will break the reconciliation report. Altough we do not advise to use the same reference twice it was not blocked when granting sub permissions therefore we now support having duplicate subpermission references in an entitlement. We still recommend removing dublicates and/or prevent getting dublicates in the granting (all-in-one) script.
• The fallback company icon (in case no icon is set in company settings) wasn’t working in the menu

• Delegated form job execution stuck in running state
• Don’t mark failed Delegated form tasks executions as finished

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 entitlements 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 Business > Rules > Entitlements. Toxic policy is now available on a separate tab (the button has been replaced).

Provisioning

• Create Business Rule from report entry
• An audit log record is now created when a rule is created or cloned, not only when it is published.
• Entitlement overview with assigned business rules

Service Automation

• Audit log for deleted product requests

• The rule mining evaluation excluded certain individuals (excluded persons) from its calculations. As a result, report entries that were fully covered by the business rules may not have been represented as such.
• In the rule mining report, the number of active persons in the configuration was previously refreshed only when the page was reloaded in the browser (F5). This value is now refreshed automatically when the page is visited, without requiring a reload.
• In the rule mining report, the number of persons shown in the entry details was capped at 100 whenever the actual number exceeded 99. This behavior was incorrect and has been corrected so that the actual number is now displayed. In addition, the summary view now shows results up to 999 instead of being limited to 99.
• In some situations, open actions could become stuck in a waiting state and appeared to hang. This issue has been addressed.

We have released a hotfix to resolve an issue where no Exchange actions were executed for the built‑in Active Directory connector when Exchange integration was enabled. This occurred when a PowerShell session without the Exchange module imported was reused for Exchange actions after previously being used for Active Directory actions.

We’ve released a hotfix to address an issue where the loading spinner in the approval inbox could continue indefinitely, and results were not displayed. This occurred in very few cases and has now been resolved.

We’ve released a hotfix to address an issue where some requests were not visible in the approval inbox. This impacted a small number of HelloID tenants and specific product requests. The root cause has been resolved, and all new requests will now appear as expected.

A new Include variables tab in the editor for advanced approval steps allows you to select built-in system variables and user-defined variables. Only the selected variables are available for use in the script. Note: The advanced approval step for approval workflows is currently available as a technical preview. While the step can be configured and validated, its results are not yet applied to live approval workflows. The feature is hidden behind a feature flag and requires a HelloID Governance module license.