Versions Compared

Old Version 3

changes.mady.by.user Betül Kara

Saved on

compared with

New Version Current

changes.mady.by.user Tina Neumann

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

After a task is finished, the following variables can be created:

  • Username of the Editoractor

  • First name of the Editoractor

  • Last name of the Editoractor

  • Email of the Editoractor

  • Current date/time when task was finished

With every loop, the variables can be created in two different ways:

...

Parameter name

Default value

Description

Valid examples

captureLoops

For every repeat, a new variable is created, which contains the loop count if it is set to true.

true

name

Username of the Editor actor will be stored if it is set to true.

true

namefirst

First name of the Editor actor will be stored if it is set to true.

true

namelast

Last name of the Editor actor will be stored if it is set to true.

true

email

Email of the Editor actor will be stored if it is set to true.

true

dateAndTime

If “true”: Current date and time will be stored with the following format: dd.MM.yyyy HH:mm

Note

The Handler doesn't work retrospective, therefore the best is in the first activity of a process, the event type “Node-Enter” to use!

dateAndTime knows of two parameters:

  • _time

  • _systemtime

systemtime can be altered to the desired format which can be used for wordtemplates, emails, dashboard etc. eg dd.MM.yyyy or dd.MM.yyyy HH:mm:ss

true

creates variable with name "taskNameStr + "_time" and value 17.03.2022 08:35

creates variable with name "taskNameStr + "_systemtime" and value 2022-03-17T08:35:00Z

creates variable with name "taskNameStr + "_systemtime,dd.MM.yyyy" and value 2022-03-17

...