Test Provisioning

Test Provisioning to verify that the setup behaves as expected before using it in production. Performing acceptance tests early helps prevent misprovisioning and reduces the risk of production incidents. Focus on validating account lifecycle and permission actions to ensure correct and predictable account management.

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.
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 one or more persons from the business rules:
- To test the business rules with a single person, set the personNr value to the ID of the selected test person.
- To test the business rules for all persons in a department, comment out the single-person test code, uncomment the for loop, and adjust the contract field name and case value to match your source data.
```
function getExcluded() {
    let contracts = source.Contracts;
    let exclude = true;

    //for loop to test with one department    
    //for (let i = 0, l = contracts.Count; i < l; i++) {
    //    let contract = contracts[i];
    //    switch (contract.pos_Dept_code) {
    //        case "I&A":
    //            exclude = false;
    //            break;
    //    }
    //}

    //code to test with one person
    let personNr = source.ExternalId
    if (personNr === '74330') {
        exclude = false;
    }
    
    return exclude;
}

getExcluded();
```
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.

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, or Manually correlate an account in HelloID using the Import entitlements report.
Delete or disable an account or remove a permission
The same business rule that grants the entitlement, will revoke it if the person no longer qualifies for it.
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. 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
Thresholds are often configured with high values before HelloID goes live. If an action is blocked by a threshold, 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.

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.
Include all persons in the business rules by removing the Excluded field from the source mapping. Then Run a manual import.

In this section: