Action templates

Facebooktwitterpinterestlinkedinmail
Applies to version: 2020.3.x and above; author: Jakub Okrzesik

 

The article is an update of the already existing article, it shows the configuration in version 2020.1.3. For the original see: https://howto.webcon.com/action-templates/.

Introduction

Action templates is a feature that allows you to save a lot of time when implementing processes and reduces the possibility of configuration errors. They allow you to create one global configuration of an action within the process, which can be used anywhere in the workflow without having to configure the action from start each time.

Where can action templates be used?

There is a scenario where we have a project that contains multiple stages that are supported by separate processes. During each stage, some parameters of the process can change which may cause inconsistencies in the subsequent stages of work. To avoid them, you can create a process that contains the history of changes of the important project parameters. Therefore, whenever a key parameter changes, we want to have a mechanism that will archive them in an instance showing the history of changes in the parameters of this project. It involves adding – at each step of each workflow of each process – an action that updates the instance containing the project history – configuring the same action on several steps of the process can be time-consuming but thanks to using action templates you can save a lot of time.

How to configure an action templates?

Templates are configured within the process, in WEBCON BPS Designer Studio in the “Configuration” section in the “Action templates” tab and click the “New template” button.

Fig. 1. Creating a new template

 

Fig. 2. The configuration of action template

 

In this window, enter the action name (template), select the action type and configure them according to your needs, you can also enter an execution condition after which action will be executed. After configuring the template, save the process. The template is visible in the tabs with available templates and you can use them.

Fig. 3. The created action template

 

To use the action template, add a new action of the same type as the template, then linking them to the appropriate template,

Fig. 4. Creating the relation the action with the pattern

 

Or directly from the template by clicking the “From template” button.

Fig. 5. Adding the new action from the template

 

After connecting the action to a template (or creating the action from template), the default execution condition for the action from the template is copied (it can be changed independently in each place the template is used) and their configuration from the workflow level is blocked – the button is grayed out.You can re-configure the entire template globally which results in immediate propagation of the introduced changes to all actions connected to the template (you can see where a template is used via the “Usages” tab).

Fig. 6. The action added from the template

 

At any time, there is the option to break the action configuration inheritance from the template, just select the “<None>” option from the template list. This will disconnect the action from the template and it can then be configured independently.

Fig. 7. Breaking inheritance the action from the template

 

Another option to create the template is to select the “New template” by clicking the right mouse button on the already created and configured action.

Fig. 8. Creating the action template

 

Summary

By using the simple action template mechanism you can reduce the time spent on configuration of actions that need repeating throughout your process. Additionally, since all actions tied to a template share the configuration, you can quickly update the configuration in the template’s configuration and all actions tied to that template will also be updated. You can also set up an independent execution condition for each action regardless of whether it is tied to a template.

Leave a Reply

Your email address will not be published. Required fields are marked *