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).
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,yes
Rule Settings
Query Section
Setting name | Description |
---|---|
Select Data Source |
This setting specifies the text file for import. The […] button allows the user to browse for the file and the Create button allows creating or editing of the file in the Cayosoft Administrator data source editor. |
The separator used in file |
Use this setting to select the separator used in the 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 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 |
---|---|
Limit scope to this OU | Specify Google Organizational Unit where the Google users will be created. |
More Options | |
Filter
|
Set the filtering conditions to only return objects or data that need to be processed by the rule. |
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 |
---|---|
9.1.0 | The rule has been introduced in the product. |
Comments
0 comments
Please sign in to leave a comment.