How to use custom variables definitions when running Rules

Article ID: 97

Last updated: 11 Jun, 2012

With release 2.4.14.7848 or higher, extra functionality was provided including the ability for you to define how variables can be read by the Riva policy. If your installation is older that 2.4.14.7848, please perform a check for updates.

You can define '[[' as a prefix and ']]' as a sufix to wrap around the ldap attribute name. This is done by creating or modifying a RivaApp.exe.config file. Following is a sample that uses [[ and ]] so you can see how this works.

The key is to define the prefix and sufix:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
       <appSettings>
             <add key="Policy.Rules.VarDef.Prefix" value="[[" />
             <add key="Policy.Rules.VarDef.Sufix" value="]]" />
       </appSettings>
   </configuration>

Save the RivaApp.exe.config file:

the \Riva\Application\Base folder for a brand new installation of Riva, or
in the latest version folder below the \Riva\Application folder, e.g. \Riva\Application\2.4.14.7848, if you have performed a successful "Check for Updates".

Each time you perform a "Check for Updates" ... Riva will copy the file to the next version folder.

With this example, I could use [[cn]]@mycompany.com or [[cn]]@[[ou]] provided that the email domain name is stored in the Description field.

If '[[' and ']]' did not work in the client, redefine the prefix and suffix to use any character string combination.

Example: Use ****! and !**** as prefix and sufix.

       <appSettings>
             <add key="Policy.Rules.VarDef.Prefix" value="****!" />
             <add key="Policy.Rules.VarDef.Sufix" value="!****" />
       </appSettings>

And [[cn]]@mycompany.com would be replaced with ****!cn!****@mycompany.com

Making it work

In a GroupWise account or resource object account, create a rule that would use the defined variable, e.g. [[cn]]@mycompany.com. In the Riva Managed Rules policy, assign that GroupWise account or resource object as the 'source' object and add the desired GW account(s) as the target accounts. Configure the rule appropriately.

When you execute the policy, Riva will read the defined variable and substitute the value that is assigned to that variable for each target account. For example, if cn=BobB is a target account, this policy would push BobB@mycompany.com in the rule instead of [[cn]]@mycompany.com.

Report an issue

Article ID: 97

Last updated: 11 Jun, 2012

Revision: 1

« Using GroupWise Resources for Managed Folders

Riva Managed Signatures: How to Remove the Logo Border »