General data mapping

In/Out

Name

Details

Data type

In

Task name

This box shows the task name that the task is to be displayed with in ARIS Process Board. If an explicit name is not modeled in the data flow, the name of the associated object of the Human task type is displayed.

The simple text structure required can be modeled as follows:

For example, connect a constant with the value Request from: with an operator of the Create collection type and with an additional constant that represents the current date. Connect the Create collection operator with the Task name box via an operator of the Format lines type.

<Text>

In

Task description

This field represents the description of the task with which the task is to be displayed in ARIS Process Board. If no explicit description is modeled in the data flow, nothing is displayed.

<Text>

In

Out

Group of executors (mandatory input)

This field represents one or multiple person(s) who carry out the object of type Human task. If an automation-relevant organizational element is connected with an object of type Human task via a connection of type carries out, a constant is automatically created. (Exception: The connection attribute is specified).

The constant contains in its value the name of the organizational element and also complex XML information.

If the input data is the XML structure that is transferred differently, the constant can be deleted. This is the case, for example, if:

  • a person selected while an object of the typeof type Human task is being carried out can be connected as input data.
  • the login name can be connected as input data via the operator Determine user via e-mail/login name.

Both options represent complex XML data.

<User>

In

Out

Login of the predefined executor (optional)

This field must be connected with the login of exactly one person from the group of executors. (If the person is not a member of this group, the assignment is ignored.)

The simple text structure required can be modeled as follows:

  • Connect a text field of an object of type Human task, into which the login information was entered manually.
  • The current user of an initial dialog can be modeled as input data.
  • You can assign the Web service as input data, which extracts the login information from an ARIS attribute.

<Text>

Out

Priority

Each object of type Human task has a priority. If no priority is specified, the priority NORMAL is applied. To define a priority as HIGH or LOW, connect a constant with the corresponding value with this field. The value must be in upper case: LOW, NORMAL, HIGH.

<Text>

Out

Throughput time

This duration represents the time allowed for performing the task. (If this time is exceeded, an escalation e-mail is sent.)

If the field is empty, the attribute Maximum throughput time of the object of type Human task is used.

If this field is connected with a duration, the time attribute is not effective.

There are two ways to define a duration:

  • As input data, define a constant and connect it with the field, or connect an object of type Human task for which the user has defined a duration.
  • With the second option, the duration that an object of type Human task may have is dynamically defined during execution.

<Duration>

Out

Task-specific escalation

If a task is not performed in the predefined time, an escalation e-mail is sent to the person responsible. If this field is not connected, an e-mail is sent to the person who is organization manager for the executor of this object of the Human task type. If this field is connected with an escalation-relevant organization element, the e-mail is sent to this role. Example: the position QM Manager has to carry out an object of the Human task type. The escalation e-mail is sent to the process manager instead of the QM manager.

<User>

Task description

Example 1 – General data mapping - Login

Example 2 – General data mapping - Login