Check
User
Use
Function Check User enables you to search for a user in the User Management Engine (UME) of the underlying Java system. You can search by a user name or ID. If the search does not return valid results, the processor of the function receives an e-mail with an attached interactive form. There he or she can enter new search criteria, and submit the form back to the system for another search.
Features
The following tables describe the items (blocks and actions) that function Check User provides.
Actions
Action Name |
Description |
CheckUserAction |
This action implements the actual search for users. The action takes a user name or ID as input, and returns the unique ID of the found user(s). If multiple users have been found, the output is returned as a structure. CheckUserAction defines three result states, which enable the system to redirect the process flow appropriately at runtime: · One user found – this is a terminal result state · No users found – new search is triggered · Many users found – the processor can select the required users from the output |
JumpAction |
This action is used to direct the flow to the target action that is assigned to the relevant result state of JumpAction. |
NewUserAction |
This action sends an e-mail with an attached interactive form, where the processor can enter new search criteria and submit it to the system. |
SelectUserAction |
This action sends an e-mail with an attached interactive form, which contains all found users. The processor can choose one of the results, and submit it to the system. In a block, the input for this action should be mapped to the output structure parameter of CheckUserAction. |
Blocks
Block Name |
Description |
CheckUserBlock |
The block flow comprises the actions described in the above table. The initial input for the block is a user name or ID. Wildcard characters, such as an asterisk (*) are allowed. The block flow goes as follows: · The initial action (JumpAction) redirects the flow to CheckUserAction. · The system checks for users according to the initial criteria. · Depending on the results, the block flow is either completed (a single user found), or redirected to NewUserAction (no users found), or to SelectUserAction (multiple users found). |
Activities
You can find the items described above in folder Predefined Content ® Check User in the gallery.
To see how it works, include it as a part of a process. Since all actions are executed in the background, in the end you will not see the result unless you also include in the workflow an additional action to display the output.