Text file | DynamicAttributes Update Google Users Properties
Rule description
This rule updates Google user attributes according to values defined in the CSV file. The data source text file must be in the comma or semi-colon separated values format (CSV).
NOTE: CSV-file should be in UTF-8 format in case of using letters with an accent: á, ä, é, í, ö, ü and etc.
When to use this rule
Use this rule when you need to update Google users' properties that depend on some other property. For example, set the various values of IPWhitelisted or IncludeInGlobalAddressList based on the primary email.
This rule queries the Google user property defined by the name of the "key" column, for example, primary email. When a user object attribute "key" attribute matches the value of the specified "key" column, the subsequent columns in the text file are used to update attributes that are defined by the remaining column names.
Example CSV File:
PrimaryEmail;IncludeInGlobalAddressList;IPWhiteListed
joe@domain.com,yes,yesRule settings
Query section
| Setting name | Description |
|---|---|
Select Data Source |
Specify the text file to be imported. The […] (three dots) button allows the user to browse for the file and the Create/Edit button allows the creation or editing of the existing file in the built-in Data Source editor. |
Separator used in file |
Specify the separator used in the source CSV file. |
More options | |
Filter CSV data |
This setting specifies the filter that can remove data rows from the imported text file that satisfies the specific condition. |
Column name > Attribute Mapping (optional) |
Use this setting to map column names from the file to the Google user attributes. When file column names do not match Google attribute names, map them here using a separated string. Map column to Google Attribute by specifying each in the format ColumnName>GoogleAttributeName. Indicate the key search column with an '*'. You can add columns that already match without formatting. Example: LastName>FamilyName,descripition |
Empty field in Data Source |
If the record in the CSV file column is empty, you can skip updating the attribute or clear its value. |
Initialization Script | |
Script |
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: Example: Update AD users, created in the last ten days.
|
Action section
| Setting name | Description |
|---|---|
| Limit scope to this OU |
This setting defines the search query scope. To improve query performance, limit the scope to a specific OU. IMPORTANT: To test the rule configuration, limit the rule scope to an OU that contains test accounts or objects and use the Preview feature. |
| More Options | |
|
Filter
|
Set the filtering conditions to hide unwanted data based on criteria not supported in the Query criteria setting. Example: filter by the found object Distinguished Name. TIP: For optimal performance, use the Query criteria setting above to filter objects whenever possible. |
Output section
This section defines the output format of this rule.
To get more information about this section, please see the Rule 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 Rule Enforce/Schedule section article.
Comments
0 comments
Please sign in to leave a comment.