Usually, rules use query criteria to limit the query search scope. It improves the performance of the executed rule.

Due to the PowerShell limitations, it is not possible to use calculated expressions in query criteria. That is the point where the initialization script can help. You can initialize a global variable in this setting and then use it in query criteria.

IMPORTANT    To use a variable, declared in the initialization script, in the query scope, it must be global: $global:<variable name>.

Example: Update AD users, created in the last ten days.

1. Add this initialization script

   Copy

   {$global:DatePeriod = (Get-Date).AddDays(-10)}

2. Use the $DatePeriod variable in the query criteria builder:

Data mapping also can be set by the script.

If you would like every provisioned user to have the extensionAttribute 1 populated with a string value, use the following script: {@{'extensionAttribute1'='YourString'}}.

If you would like every provisioned user to have the extensionAttribute 2 populated with the corresponding value from the column in your data source file, use the following script: {@{'extensionAttribute2'=$_.EXT2}}. EXT2 is the name of the column from your data source.

NOTE    If you set mapping for the same properties both in the Properties mapping and Properties mapping script, attribute values will be updated by the script.