Test Provisioning

Test your Provisioning setup to verify that it behaves as expected before using it in production. By performing acceptance tests early, you can confirm that account llifecycle and permission actions work correctly and avoid misprovisioning or unexpected outcomes.

To minimize risk, start by testing your configuration with a single person. This allows you to validate your business rules and provisioning in a controlled way, without impacting other accounts. Once validated, you can proceed toward broader use in production.

Prepare persons and business rules

Follow the steps in Set up Provisioning up to and including step 5 (creating business rules).
Create or select one or more test persons:
- Create a test person in one of the Source systems and Run a manual import. The person should appear in the list of imported Persons in HelloID.
- Select a test person from the already imported Persons in HelloID.
For testing purposes, you should have access to the relevant source systems, or team up with someone who does.
Tip
Select a person with a relatively complex name for HelloID, for example, a compound last name that includes both the partner’s name and the birth name. This also allows you to validate the naming conventions configured in HelloID.

Exclude all persons from the business rules except the test person or persons, following the instructions in Exclude persons via source mapping. Select the Complex mapping type.

Use the following code, with a few adjustments, to exclude selected persons or departments from the business rules.

To test the business rules with one or more persons, add the ID of the test person(s) to includedPersons.
To test the business rules for all persons in a department, add the department code to includedDepartments, and replace department_code with the name of the contract field that contains the department code.

function getExcluded(){
    const includedDepartments = ["department1","department2"]; // Add all department codes of departments you want to include
    const includedPersons = ["123456","456789"]; // Add the externalID of all persons you want to include
    let returnObject = true;
    if(includedPersons.includes(source.ExternalId)){
        returnObject = false;
    }else{
        source.Contracts.forEach(function(element){
            if(includedDepartments.includes(element.department_code)){ // Edit the contract field used for the department code 
                returnObject = false;
            }
        });
    }
    return returnObject;
};
getExcluded();

Alternatively, edit the relevant business rule: Add a person condition and set it person.ExternalId to match the ExternalID of the test person(s).

Publish draft business rules that you want to test. Only business rules that you want to test should be published.
Clone all published business rule that you do not want to be applied; see Clone a rule. The duplicates are identical to the published rules, but they are in a draft state. This effectively disables the business rules. Remove the published version of the business rules that you cloned.
Target system thresholds are often configured with low values until HelloID goes live. To ensure that no unintended actions occur, adjust these values to match the number of test subjects. For example, if you are testing with one person, set the thresholds to 1.

Prepare entitlement action test cases

Create or enable an account, or add a permission or group membership
Publish a business rule or ensure there is a published business rule that grants the account, account access, or permission entitlement.
Or, temporarily Add an entitlement to a rule and publish the rule.
Verify that the test person is in scope of the relevant business rule: go to Business > Rules, click the rule and look for the test person under Persons. If necessary, modify the person's data in the source system.
Correlate an account
Correlation links an existing account to a person in HelloID when the following conditions are met: the person is entitled to an account, the person does not already have an account that is managed by HelloID, and the account and person share the same correlation value.
The easiest way to create this situation is to unmanage the account created for the test person in test case 1. Unmanaging the account causes HelloID to forget that the person has an account, while the account itself remains in the target system with the same correlation value.
Alternatively, you can manually add the person's correlation value to an existing account in the target system (see Manually correlate an account to a person), or Link an account to a person (Import entitlements report).
Delete or disable an account or remove a permission
If the person no longer qualifies for the entitlement based on the published business rules, the entitlement is revoked.
Modify the test person's data in the source system accordingly.
Then Run a manual import.
Verify that the test person is no longer in scope of the relevant business rule: go to Business > Rules, click the rule and look for the test person under Persons.
Update an account or permission
Modify the test person's data as required. Then, Run a manual import.
Tip
A key test case is a change of department or job title. This represents the Mover scenario in the JML (Joiner, Mover, Leaver) user lifecycle.
Another common test case is a name change, such as after marriage or divorce.
Note
An update in a system that has dependent systems will trigger an update in all dependent systems.

Test procedure

Per test case:

Prepare the test, depending on the entitlement action test case.
Run an evaluation and ensure the desired entitlement action is listed on the Business > Evaluations > Actions tab.
Run an enforcement.
Or, Run with resources if the entitlement action (e.g., grant a group membership) can only take place if a resource (e.g., a group) is first created by HelloID.
Note
An enforcement applies all published business rules for all persons that are not excluded from the business rules.
Go to Business > Entitlements > History and verify that the desired entitlement action ran successfully.
Tip
If an action is blocked by Target system thresholds, go to Business > Entitlements > Blocked, and click Approve for the blocked action.
Verify that the person's entitlements and data in the relevant target system and any dependent target systems are as expected.
Verify that any configured Notifications were sent.

Post-test procedure

After completing all tests:

If HelloID has not gone live yet: duplicate published business rules, keep the draft versions and remove the published versions. This way the business rules cannot be enforced for all persons by accident.
Revert changes to business rules made for testing purposes.
Set the Target system thresholds to their original values.
Include all persons in the business rules by removing the Excluded field from the source mapping. Then Run a manual import.

In this section: