Rule description
This rule queries the specified Active Directory scope and for each user in this scope finds a record with the same anchor in Workday and updates this record with attribute values that are specified in the Attribute mapping setting.
When to use this rule
You can use this rule when performing bulk user account updating from the Active Directory into the Workday HR system.
Rule Settings
Query Section
| Setting name | Description |
|---|---|
|
Workday endpoint URL |
Specify Workday endpoint URL. By default, the value is taken from the Workday HR extension. |
|
Workday credentials |
Specify Workday credentials. This account must have proper API permissions in the Workday tenant. User format: user@tenant. By default, the value is taken from the Workday HR extension. |
|
Limit scope to this domain or OU |
This setting defines the search query scope. To improve query performance, limit the scope to specific OU.
Important: To test rule configuration, limit the rule scope to an OU that contains test accounts or objects.
|
|
Query criteria |
Query criteria are sent to the Active Directory with other query parameters to reduce the number of objects returned. |
| Hours to sync
|
Specify how often synchronization will be run (every number of hours). |
| Active Directory Anchor attribute |
Defines the attribute in the Active Directory to which the Data Source anchor attribute is to be compared. When a new user is created this value also specifies the Active Directory attribute into which the Data Source anchor is written for comparison the next time the rule is executed.
Note: If the Active Directory attribute you wish to use as the Active Directory Anchor attribute is not displayed, you can enter the LDAP name of the attribute in the field. The attribute must be flagged as searchable (https://msdn.microsoft.com/en-us/library/ms679765(v=vs.85).aspx) within Active Directory. To determine if the attribute is flagged as searchable you can use ADSI Edit to view the Schema Objects container and examine the attribute’s searchFlags property.
|
| Data Source Anchor attribute |
Defines the Data Source attribute that will be used to determine if the user account already exists. This value is compared to the Active Directory Anchor Attribute. |
|
Other Query Settings |
|
| Properties to display |
To display additional properties for each object found by the query, add those properties to the list. |
| System properties | List of properties required for this rule to be executed correctly. |
| Filter |
To hide unwanted data based on criteria, not supported by Active Directory query, set the filtering conditions here. Example: filter by the found object Distinguished Name.
Tip: For optimal performance, use the Query criteria above to filter objects whenever possible.
|
| Sort by | Sort the result object list by selected attribute. |
| Initialization script |
Usually, rules use query criteria to limit the query search scope. It improves the performance of the executed rule. Due to 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.
{$global:DatePeriod = (Get-Date).AddDays(-10)}
|
Action Section
| Setting name | Description |
|---|---|
|
First name Middle name Last name Preferred first name Preferred middle name Preferred last name Work number Work email |
Specify if the attribute should be updated and if it does select the attribute to update the value from. |
Output Section
This section defines the output format of this rule.
To get more information about this section, please see the Output section article.
Enforce/Schedule section
This section defines the schedule for how often to run the rule.
To get more information about this section, please see the Enforce/Schedule section article.
Change History
| Version | Notes |
|---|---|
| 11.2.0 | The rule has been introduced in the product. |
Comments
0 comments
Please sign in to leave a comment.