Adaxes Web Interface Help | Show AllHide All |
When you update multiple objects, set patterns for object creation and modification, define some Business Rule, Custom Command, or Scheduled Task actions, you may need to specify unique property values for each object that is updated, created or modified. You can do so with the help of value references. A value reference is a pattern of text that contains the name of the property it refers to and some formatting options. When a value reference is resolved, it is substituted with the value of the referenced property. For example, the %mail% value reference will be substituted with the value for the Email property (johndoe@company.com).
Value Reference Usage:
Updating multiple objects. In Adaxes, you can update multiple objects via the Add/Modify Property wizard or Property Pages for multiple selections. When doing so, you may need to specify unique properties for each object. This can be done with the help of value references. For example, you can specify unique web pages for multiple users via the following pattern: www.%username%.company.com. The value reference %username% in this pattern will be replaced with the value of the samAccountName property of each user. So, each user will get a unique web page based on his/her own properties (i.e. www.jdoe.company.com).
Performing Exchange Tasks in bulk. To perform Exchange tasks on multiple objects at once, you need to use value references. For example, you can create Exchange mailboxes with unique Exchange alias for multiple users via the following pattern: %firstname%%lastname%. This pattern will be replaced with the values of the First Name and Last Name properties of each user. So, each user will get a unique alias composed from his/her own properties.
Facilitating object creation and modification. Adaxes allows you to facilitate object creation and modification by auto-populating property fields using already entered information (via Property Patterns). With the help of value references you can define patterns for auto-population. For example, in a Property Pattern for users, you can specify the %lastname%, %firstname% pattern for user's Full Name property. In this case, when a user is created, the Full Name field will be auto-populated with the values of the Last Name and First Name properties while they are entered. The resulting value will be as follows: Doe, John.
Defining Business Rule actions. Business Rules perform additional actions, when a specific operation is executed on AD objects. To define these additional actions, you can use value references. For example, you may want new user accounts to contain information about their creator. For this purpose, you can create a Business Rule, executed when new users are created, that updates user's Description property according to the following pattern: Created by %initiator%. The %initiator% value reference will be replaced with the logon name of the user who creates a user account. So, description of each new user will contain information about the creator of this particular object, i.e. Created by johndoe@company.com.
Setting up Custom Commands. Custom Commands allow you to execute multiple actions for a specific repetitive task in one operation. To set up actions to be included in a Custom Command, you can use value references. For example, a Custom Command can execute a script on AD objects. The data on these objects is transferred to the script with the help of value references. E.g.: cmd.exe /C echo Name="%fullname%" Logon Name="%mail%" > C:\%username%.txt. The value references in this script are replaced with the property values of the objects, on which the Custom Command is executed, so you don't have to enter script parameters manually every time.
Specifying parameters for Home Page actions in the Web Interface. Adaxes allows you to launch frequently used operations right from the Home page in the Adaxes Web Interface. When specifying parameters for such operations, you can use value references to insert property values of the operation initiator. For example, in the Create Object operation you can set default property values for new objects. These default values can be generated automatically based on the properties of the object creator. E.g.: if you set the default value for the Manager property to %distinguishedName%, the Manager property of a new object will always be set automatically to the DN of this object creator.