When your form project includes a table from which the (Helpdesk) user
can make a selection, the selected data will have to be processed. To
understand how this works, we need to have a closer look at UMRA.
In the UMRA architecture, the form project as presented to the delegate
user in UMRA Forms (client) has
been separated from the actual script. In other words, the UMRA project
as shown on the client side does not contain any scripting. The project
script, developed by the administrator in the UMRA
Console, is part of the project maintained by the UMRA
Service. The script actions in this project script make use of
variables. As soon as a delegate user hits an action button in the project
form on the client side, the following data are submitted to the UMRA service:
the project form ID
the name of the variables and their corresponding
values
the ID of the button which has been clicked
The UMRA Service then retrieves
the project with the corresponding project ID from the forms database
and executes the script of the project, substituting the variables in
the script actions with the actual values. This principle is shown in
the figure below.
Submitting variable
values to the UMRA Service
In the case of form tables, table columns can be assigned to a variable.
This could be a table column holding the distinguishedName
attribute as part of an LDAP table .
Assigning variables
to table columns
The distinguishedName attribute
uniquely identifies users with the full LDAP string. For example:
CN=John Johnson,OU=Marketing,DC=T4EDOC,
DC=LOCAL
When the user hits the action button in the form, the variable %DN%
for the selected user ( e.g "CN=John Johnson,OU=Marketing,DC=T4EDOC,
DC=LOCAL") is submitted to the UMRA Service. The UMRA Service then
executes the script (e.g. Get
User (AD)) of the project, substituting the variable %DN% in the script
action property LDAP name with its actual value
Passing a variable holding
the distinguishedName attribute to the Get
user script action
