Test account and permission scripts
Add process logging to the scripts. See Process logging in PowerShell target connectors.
First test the account and permission scripts using the Preview button in the script editor.
For Separate permission scripts (i.e., grant, update and revoke action scripts), a permission must be selected. Clicking the Sync button refreshes the list of available permissions.
Log messages appear in the Preview area of the script editor, under Logs.
Follow the steps in Test Provisioning.
Note: The Test Provisioning procedure was written for acceptance testing and presumes that source systems, business rules, and target systems are already configured. Depending on the current state of your environment you may need to adjust the configuration to properly test your account and permission scripts.
If you cannot select any persons to test with, add a source system of which the import persons script creates a number of dummy persons, for example, the Source Template from Tools4ever's GitHub resources. Then Run a manual import and select one or more test persons.
If no business rules have been set up yet, create a business rule that applies only to the test person(s). Add a person condition: person.ExternalId, and set it to match the ExternalID of the test person(s).
Modify the business rule, the test person's data (for example, by modifying the import persons script of the source system), or one of the fields in the source mapping or target mapping to align with your test scenario.
Check the target system and the script log messages; see Process logging in PowerShell target connectors.
If the script failed, use the log output to identify and resolve the issue.
If the action fails for another reason in a production environment, Troubleshoot entitlement actions.
Once the script has run successfully and has the desired effect in the target system, revert the changes to your environment that were made for testing and remove superfluous process logging commands.