Each script action has a predefined set of properties. A property specifies
a characteristic of an action. To setup a script action, you need to specify
the values for the script action properties but you cannot add or remove
properties from a script action. For more information on projects, scripts,
actions and properties, see Different
project types and Principle of
operation. To set the value for script action property, select the
script action in the lower left part of the project window. Once selected,
the script action properties are shown in the lower right part of the
project window.
In the example shown, the selected script action is Create
user (AD). In the lower right
part of the window the properties are shown. In this example the selected
property is SurName with value %LastName%. To specify the value of a property, double
click the property or select menu option Actions,
Properties of action property.
The Properties
window shows up:
The window shows the name of the property,
a description of the property and in the bottom section of the window,
you need to specify the value of the property. You have three options:
Value specified
as a constant value: Select
option Use the following value. In this case, the value of the property
is set to a fixed constant value. You can use this option only if the
property value must be the same each time the script is executed. This
method is advised for fixed constant properties that have a value that
is not used for other properties of the same or other script actions.
Examples: the password flags (user cannot change password, password expired),
the flag indicating if a share must be created for a home directory. These
values are probably the same each time the script is executed.
Value specified
as a variable: Select option
Use the following value. With this option instead of specifying
a value you specify the name of a variable. By default, the name of a
variable should be enclosed with %-characters. At run-time, the name of
the variable is replaced by the value of the variable. There are 2 major
reasons to use variables: link
to input data: a column of the
input data specifies the value for the variable. If you want to use the
value of a column from the input data in a script, you need to use variables.
In the example shown, the second column of the input data contains the
last name of the user accounts that must be created. For script action
Create user (AD)
the value of property SurName is set to variable %LastName%. Next, the second column is linked to variable
%LastName%.
For more information in this topic, see Project
operations - Variables. The second reason to use variables is to simplify
the configuration of script action properties. This happens when multiple
script action properties should get the same constant value. In this case
you can specify the constant value for each property but you can also
introduce a variable at the beginning of the script and specify the variable
name for the script action properties. Example: if you setup a user account
and associated resources (mailbox, group membership, home directory, ...)
you need to specify the name of the domain for various properties of these actions.
Instead of specifying the name of the domain as a constant for each of
these properties you can also introduce the variable %Domain%
as a separate script action
and set the value to the target domain. Next, you can specify the value
%Domain%
for all script actions properties that should contain the name of the
domain. Note that a variable is automatically created if you specify a
variable name %...%.
Value not specified: Select option Do
not specify a value for this property.
Some action properties are mandatory, others are optional. For optional
properties, you do not always need to specify the property value. For
instance, if you don't want to use it, you don't need to specify Active
Directory attribute Phone number for a user account.
Output properties
The result of some script actions can be used by subsequent script actions.
In User Management Resource Administrator, this is accomplished by using
output properties. For these properties, the result corresponds with a
value that is stored in a variable. This variable can then be used as
a property value in subsequent script actions. For more information, Project operations - Variables.
