What determines the start and end point of a ##[CurrentUser.Id] in a process?

[NoxParticipant]

Hi

The id is always set to the “active” user that is currently executing a process or a form activity.

- The user starts a new process instance via the dashboard, which is executed synchronously - the currentuser.id is set to the id of the user
or

- The user starts a new process that has no manual tasks (such as forms). Therefore the whole process and its activities get queued, and the engine executes every activity asynchronously under a generic user name (most of the time, its [email protected])

So it is a question of the current session scope. Everything executed within the user session (blocking/waiting until it’s finished) will have the currentuser.id filled with the executing user, everything else, running in the background, will have a generic engine user id.

In case you need the initial user ids beyond the blocking/synchronous tasks, you can store them in a variable.

I hope this helps.

BR

• This reply was modified 3 years, 9 months ago by Nox.
• This reply was modified 3 years, 9 months ago by Nox.
• This reply was modified 3 years, 9 months ago by Nox.

[Author]

Posts