Provisioning

It would be nice to have the possibility to correlate on custom added fields added in the mapping of the Target Systems. There are some customers where the account key is stored in not default fields available in the correlation settings.

On the Contracts tab under Persons, the Primary contract is always shown on top, but the other contracts are seemingly shown in a random order. It would be nice to apply the sorting defined in the Primary contract configuration to this contracts overview. This would make the mechanism more understandable and allow customers to understand why a contract is primary and the other not when actively using more then one criteria. This is already implied because the primary contract configuration is a sorting mechanism, and the primary is the top contract, however not shown on the contracts tab.

Could the username of who run the import be shown within the "Information" tab.

I really would like to see what actions specifically are being blocked before allowing them. I mean, they are blocked because so you can check if you really want all those many updates. Therefor it would be nice to be able to see what you let through.

Add the ability to the PowerShell target connector to create entitlements using a UI instead of using dynamic PowerShell. This allows us to manually create entitlements easily on which we can have our own actions. For example, a system doesn't support setting the permissions trough an API in this case we can create the entitlements as permission and send an email when the permission is granted or revoked. Have option available to choose between static table or dynamic PowerShell (just like OU selection) on entitlements When static selected show a table for which new rows can be created. Have the ability to add and remove columns from the table. Add grid control having the ability to dynamically add columns. Minimum requirement support for 2 columns (identifier, displayName).

We would like to configure a key on the source so when the key for two or more sources is equal we can use this so no new person is created when the second person identification key (employeeNumber as an example) is equal. This allows us to switch to a new source system with the same person key without losing the current persons and entitlements. We should warn the customer for changing the key because it could lead to removing all persons from HelloID.

I'd like to see the raw data viewer on the departments, this would help me in diagnosing issues with manager resolving and department mapped fields.

As a HelloID Administrator, I would like to have the {{Account.}} object available besides the {{differences}} object inside the account post update action. In this way it can be used parameterized when sending email notifications based on using extended account data of the post action script.

Please add the number of entitlements and the number of entitlements per category (Granted, Failed Grant, Failed Revoke, Pending, Blocked, etc)

The current values in a CSV export are comma-separated. This is not ideal because text fields quite frequently also contain commas. For example the displayname. A different default separator (for example ";") would save a lot of time that is now needed to get the data in the right columns.