pipeforce.event.workflow
Every 123 workflow topic key can additionally contain dynamic values which will be replaced at runtime such as:
{appName} = Will be replaced by the app name the workflow is stored inside (example: io.pipeforce.myapp).
{wfName} = Will be replaced by the property name of the workflow definition in the workflow folder inside the app (example: myworkflow)
Workflow address variables ($uri:wf-)
In case a push event is a workflow event (pipeforce.event.workflow.#), these additional address variables can be used in TO, CC and BCC fields to refer to data from the event message:
$uri:wf-authenticated-user= Returns the$uri:user:<username>of the user who was logged-in at the time of this event and potentially has initiated this event.$uri:wf-process-involved-users= Returns the$uri:user:<username>of all users involved in the workflow process.$uri:wf-started-by= Returns the$uri:user:<username>of the user who started the workflow.$uri:wf-task-candidate-groups= Returns the$uri:group:<name>names of all groups which are set as candidate group of given task. In case there is no candidate group set, the address variable will be removed from all address fields.$uri:wf-task-assignee= Returns the$uri:user:<username>of the user who is set as assignee on given workflow task. In case there is no taskAssignee set, the address variable will be removed from all address fields.$uri:wf-task-owner= Returns the$uri:user:<username>of the user who is set as assignee on the given workflow task. In case there is no taskOwner set, the address variable will be removed from all address fields.$uri:author= In case the event is related to a comment creation, returns the$uri:user:<username>of the user who created the comment. This is also true for comments created outside of workflow related events.
Duplicate addresses will always be removed.
.comment.create
This event message is send after comment to a workflow process was created.
The full structure of the event message routing key is like this:
pipeforce.event.workflow.comment.create.{appName}.{wfName}.{commentUuid}
.comment.update
This event message is send after comment to a workflow process was updated.
The full structure of the event message routing key is like this:
pipeforce.event.workflow.comment.update.{appName}.{wfName}.{commentUuid}
.end
This event message is send after a workflow process have been finished.
The full structure of the event message routing key is like this:
pipeforce.event.workflow.end.{appName}.{wfName}
.task.assignment
This event message is send after the task assignee has changed.
The full structure of the event message routing key is like this:
pipeforce.event.workflow.task.assignment.{appName}.{wfName}
.task.complete
This event message is send after a task was completed.
The full structure of the event message routing key is like this:
pipeforce.event.workflow.task.complete.{appName}.{wfName}
.task.create
This event message is send after a new task in a workflow process was started (created).
The full structure of the event message routing key is like this:
pipeforce.event.workflow.task.create.{appName}.{wfName}
.task.delete
This event message is send after a task was deleted.
The full structure of the event message routing key is like this:
pipeforce.event.workflow.task.delete.{appName}.{wfName}
.task.timeout
This event message is send after a task timeout happened.
The full structure of the event message routing key is like this:
pipeforce.event.workflow.task.delete.{appName}.{wfName}
.task.update
This event message is send after a metadata or variables of a task have been updated.
The full structure of the event message routing key is like this:
pipeforce.event.workflow.task.update.{appName}.{wfName}
.transition
This event message is send after a (task) transition have been occurred from one state to another.
The full structure of the event message routing key is like this:
pipeforce.event.workflow.transition.{appName}.{wfName}
.start
This event message is send after a new workflow process have been started.
The full structure of the event message routing key is like this:
pipeforce.event.workflow.start.{appName}.{wfName}
0 Comments