Provisioning

When doing maintenance tasks in HelloID Provisioning (like migrating/upgrading source- or targetsystems) it would be useful to set a maintenance mode (e.g. textbanner or lock) so that only the person who is doing maintenance can start new imports/snapshots/evaluations/enforcements. This prevents that other portal users make changes in the provisioning module that could disrupt the provisioning process.

In the $ outputContext.Data and $outputContext.PreviousData objects, we currently return the new and old data to HelloID. We would like to see a standard audit logging message whenever there are differences between the new and old data. This logging should include the old and new values, along with the corresponding fields. Currently, we calculate these values in some PowerShell connectors, such as EntraID or TOPdesk. The benefits of moving this functionality to HelloID include reduced PowerShell code complexity and increased consistency across target systems. Example: Old values: DisplayName: Janine van den Boelen Surname: van den Boelen New values: DisplayName: Janine de Vries Surname: de Vries

I would love to have more options in the business rule drop-down conditions. Now we have the option to select person attributes or contract attributes, but for Departments and Titles there is an exception where we have drop-downs. These are very helpful and make the business rule more readable. I would like to extend these drop-downs to other parts of the contract, like CostCenter, Location, Organization and Team, as these are often used for business rules. This change will improve readability and help people to understand the conditions more easily.

Right now a user needs admin access to HelloID and gets full access to the Provisioning console. We would like to be able to grant someone only access to persons and/or business rules only.

we would like to have a version history of all parts of HelloID provisioning that is restorable, like we had in IAM.

I would like to have the option "or" in the custom events conditions for using in e-mail notifications. So that only one of the conditions needs to be true. For example: I created 2 seperate custom events: function change department change When both conditions changes for a user, I get 2 e-mail notifications instead of one combined e-mail notification. Because you can only use one custom event per notification. Workarround is to create 3 custom events with the following conditions: when function is updated and department is not updated when function is not updated and department is updated when function is updated and department is updated

As an administrator, on new PowerShell target connector, It would be nice not loosing the complex mapping script when switching from complex mapping to other and coming back to complex mapping.

Add the possibility to select a notification type from a notification system in business rules.

Although the import-module method is not allowed in Powershell Core it would be nice to be able to import the EXO module in Powershell Cloud for tenants that do not use an On-Premise HID Agent.

Provide an API to mass import business rules. Clients will usually have a mapping for department or job title to specific entitlements. Entering these manually can be a lot of work. Using an API to import (or even from CSV) will allow customers to quickly get started