Skip to main content

General settings

Variables and Functions

There are several ways to integrate dynamic information into your workflow. For example, you can use the current selection from the map, or you can reference to an additional FormField.

Session

In workflows you can store and retrieve information to the session which is stored in the tenant database and is available during navigation in the workflow tree or interacting with a form or a list.
The session is filled automatically (for example, if an element is selected in a list, the id of the selection is stored in the session) or can be defined by the workflow creator (for example, by using saveinsessionattribute in a FormField).

Syntax

  
{SESSION.TABLENAME.PRIMARY_KEY_COLUMN}

Example

  
{SESSION.EDIT_AREA.ID}

Form

Within a Form you can also reference to an other FormField's value to define the default value, lov and other attributes.

Syntax

  
{FORM.FORMFIELDNAME}

Example

Let's assume that you want to drill down an address within a country by using multiple FormField's. The first one to select the city, the second one to select the street and the last to pick the street number. As soon as you select or change the city, the street combo box should be updated to only shown the streets within the selected city.

  
<FormField name="CITY" label="City:" datatype="number" type="combobox" 
		lov="SELECT ID, NAME FROM CITY" />
<FormField name="STREET" label="Street:" datatype="number" type="combobox"
		lov="SELECT DISTINCT(ID), NAME FROM ADDRESS WHERE CITY_ID = {FORM.CITY}" />
<FormField name="STREET" label="Street:" datatype="number" type="combobox"
		lov="SELECT ID, HOUSENUMBER FROM ADDRESS WHERE CITY_ID = {FORM.CITY} AND STREET_ID = {FORM.STREET}" />

Requestcontext

Additional "Url"-Parameters not covered by Workflow-variables can be accessed via request context variables.

Syntax

  
{REQUESTCONTEXT.MYURLPARAMETER}

User

In some cases the workflow designer also needs information about the user within the workflow. Possible use cases:

  • Storing the name or id of the user how has created or last modified the record
  • Sending a notification to the user via email
  • ...

Following user information can be requested:

  • {USER.Identifier}: Unique ID of the user
  • {USER.Name}: username within the current session
  • {USER.Description}: the description stored to the user
  • {USER.Email}: the email address of the user

Syntax

  
{USER.Keyword}

Map

There are special session variables which are related to the state of the map (e.g. scale, visible features, ...) when the workflow was called.

Available variables:

  • ActiveFeature
  • MapScale
  • MapBounds
  • MapCenter
  • MapSelection

Syntax

  
{SESSION.MAP.Keyword}

Example

  
{SESSION.MAP.ActiveFeature}