Skip to end of metadata
Go to start of metadata

 

 ← Return to the list of available actions

If you have a problem understanding how the action works, check: ActionConditional ExecutionComponents parameters.

Basic information

Category: User

Previous names: Downloading user data (up to version ???)

Action location: Variable, Button, Form

Available from version: 1.0.27

Description

An action that searches for user data based on the given login and writes it to the header or table variable.

In case of a header variable, subsequent values are separated by semicolons, e.g. "anowak;jpawlak;knowacki". If there is no value, it is saved an empty string to the variable "".

In case of a table variable, subsequent values are saved in subsequent cells of the column.

Data possible to obtain:

  • First name
  • Last name
  • Email
  • Full name
  • Number
  • User group names
  • User's position names
  • User’s position symbols
  • User's organizational units symbols
  • User's organizational units names
  • User's superior's logins
Action call-up

Leaving an empty conditional field is equal to setting it to "true".

Action location Parameter operation "Conditional execution" Action call condition
Form buttonActivates/deactivates the action call after pressing button Pressing button 
Form variable 

Activates / deactivates the action call after changing the variable value

Call action 

Variable value change 

Parameter "Conditional execution" will return "truth" 

FormCall action Parameter "Conditional execution" will return "truth" 
Configuration parameters
Parameter nameFrom versionDescriptionParameter typeDefault valueField typeComments and restrictions
User login*1.0.27User login whose data will be saved to variables.Text Editable fieldIf the application does not find a user with the given login, it will throw an error.
Data type*1.0.27User data types that will be saved to variables.Text values table Non editable dropdown list

Previous name: Selected data. Note - in older versions, it was necessary to enter the type of data manually. Available values from that period can be seen in the table below.

Data typeFrom versionParameter value to enter (without using the drop down list)
First name1.0.31

FIRSTNAME

Last name1.0.31LASTNAME
Email1.0.31EMAIL
Full name (first and last name)1.0.31FULLNAME
Number1.0.31NUMBER

User group names

1.0.31GROUPSNAMES

User's position names

1.0.31POSITIONSNAMES

User’s position symbols

1.0.31POSITIONSSYMBOLS

User's organizational units symbols

1.0.31POSITIONSOUSYMBOLS lub OUSYMBOLS (obie wersje poprawne)

User's organizational units names

1.0.31OUNAMES

User's superior's logins

1.0.27SUPERIORSNAMES
Variables for data storage*1.0.27Variables in which user data will be savedVariable Editable field

Variables should be of text type - header or tabular. In the case of headers, subsequent values will be passed after the semicolon, e.g. "position1;position2;position3". In the case of table variables, subsequent values will be saved in separate rows of the column.

Parameter*- mandatory field

Configuration example

 Example 1
Example

 

Suppose there is a user who validates invoices and issues them to clients. However, before it, one of that user superiors must approve the invoice.
The problem is that the document must contain the full name issuing the invoice user, but you have only access to the login. In addition, you do not have saved information about who is the user's superior.


To solve this problem, you can use an action that will save the data for it in the selected variables for the given user's login.
You should configure the "Download user data" action as follows:

Where:

Checker login - is a text variable that stores a user login that checks and issues invoices.

The person issuing the invoice - is a text variable in which you want to save the user's full name in order to later transfer to the document.

Accepting person - is a text variable in which you will write down all user's supervisors after the semicolon - note that properly handle both one and many returned values!

In this way configured action is placed in the appropriate form on the process map. The result should appear after loaded the form by user.

Change log

1.0.27

  • Adding a component that download information about supervisors

1.0.31

  • Data types support adding: 
    • First name
    • Last name
    • Email
    • Full name
    • Number
    • User group names
    • User's position names
    • User’s position symbols
    • User's organizational units symbols
    • User's organizational units names

1.0.??

  • Changing the name from "Downloading user data" to "Download user data"

  • No labels
Write a comment…