This page allows you to create actions with one or more post-functions that can be used in the Shared Action post-function. This feature can be used to share the configuration of a single /multiple post-functions between transitions/workflows thereby reducing rework while modifying the post-function configuration. For example, for an employee onboarding process across projects instead of adding the , or of a sequence of post-functions in transitions across all workflows, you can create a Shared Action with all the post-functions and use this action in the Shared action post-function, between multiple transitions and workflows, thereby greatly simplifying the maintenance of your workflows.
On this page:
Table of Contents |
---|
...
Passing variables within a sequence
Using the {% setContextVar %}
Nunjucks tag, you can pass data from one post-function to its subsequent post-functions.
transition.context: Holds all the context variables added in the current post-function. For example: Create , if you create a context variable
myVar
in the first post-function of the sequence:Code Block language js linenumbers true {% setContextVar myVar = "a value" %}
This variable will now then be available to its subsequent to subsequent post-functions as:
Code Block language js linenumbers true {{ transition.context.myVar }}
Note , that this variable will not be available in the Nunjucks tester.
...