> |
|
Go to: Homepage User Management Resource Administor. Bulk user import software. |
|
There are several ways to add actions to a script. For a basic understanding of projects, input data and scripts, see Principle of operation. With the following operations you can add an action to a script. Note that a project window must be open to perform these operations:
Select the script action in the Actions bar and select menu option Actions, Add action to script, or right click on the script action and select the menu option.
Drag and drop the script action from the Action bar to the script area of the project window.
Drag and drop a script action from another project to the script area of the target window. In this case, all the properties are copied to the new project as well.
The position of a script action in a script is important. If the order is not correct, the script cannot be executed correctly. Example: if you create a user account and Exchange mailbox, the action to create the user must precede the action that creates the Exchange mailbox. To move a script action in the script to another position, drag and drop the script action to the desired position.
To delete a script action from a script, select the action and press the Del key or select menu option Actions, Delete script action.
By default, script actions are executed in the order as they appear in the script. But depending on the result of script actions and by special variable actions you can control the order in which script actions are executed. With these possibilities the script becomes a program with conditional jumps and better controller action execution. From this point of view, User Management Resource Administrator is a programming language to program the Windows network. To change the order in which actions are executed, labels are used for script actions. A label refers to a script action. To set a label for a script action, select the action in the script of the project (lower left part of the project window) and select menu option Actions, Set script action label. Each action can have only one label. When script execution continues at a label, the next action executed is the action with the specified label. If no action has the label specified, an error is generated and script execution is stopped. Note: since you can also jump to previous script actions, you can introduce deadlock situations where script execution never ends. It is the responsibility of the user to prevent this situation from happening. There are two general ways to change the order used to execute the script actions, described in the sections below.
When the execution of an script action fails, you have several options to control the execution of script action. To specify these settings, select the action in the script of the project (lower left part of the project window) and select menu option Actions, Script action error handling.
|
Option |
Description |
|
Continue with the script . |
If this script actions encounters an error, it will (try to) continue normally with the next consecutive script action in the script |
|
Jump to the script action with label xxxx |
If this script actions encounters an error, it will jump to the script actions specified by the here specified destination label |
|
Terminate the script but continue the session with the next line |
If this script actions encounters an error the current script execution is terminated. The session continues by running the script with the next line of input. |
|
Terminate the session |
If this script actions encounters an error the current script execution is terminated and also the current session is terminated |
The GOTO script action is used to continue script execution with another script action than the next script action. The referenced label can be a variable name.
More information:
Principle of operation
Project operations - Input data
Project operations - Variables
Help on help
|
Copyright ©2003 - Advanced Toolware LLC. All rights reserved.
|