To add a system action building block to a task path workflow

The procedure to add a system action building block to a task path workflow is as follows:

Prerequisite procedural steps are covered separately in the topic To configure the workflow structure of a task path definition. Refer to these before proceeding to step 2.
With the Path tab activated, use the Version drop-down field to ensure that the correct variant of the task path workflow structure is displayed.
Using the standard 'drag and drop' technique, transfer a new System Action () building block to the design area. The Configure System Action - Select Action window is displayed.
Enter a Name for the new system action instance into the field provided 1.
Using the Action type drop-down field, select a parameter value to control the method by which the system action is defined i.e. Launch Pop-up, URL, Process, Stored Procedure, Web Service or Create Linked Case; choose the corresponding System Action trigger from the filtered subset. An explanation of each option is detailed in the table below.
Where the system action can be initiated without end user qualification, activate the Run automatically tick box provided. Otherwise, select the desired ownership rules using the inter-related Allocate to case owner (tick box) and Allocate to case users / Allocate to case roles (multi-select) options 1.
Where execution of the system action is Mandatory, activate the corresponding tick box provided.
To prevent the system action from being regenerated for a reset task path, activate the Do not repeat tick box provided.
Where the system action needs to be repeated at a predetermined frequency, activate the Recurrent task tick box provided.
Using the SLA definition drop-down field, select an overarching target completion framework appropriate for the system action building block.
Using the Loop back points drop-down field, multi-select all previous component building blocks within the task path workflow structure to which progression focus can be returned, or choose the All option, as required 2.
Click on Next. The Configure System Action - Define Inputs window is displayed, ready to configure the input parameters applicable to the system action. For each parameter listed, define the relevant Source type that will be used to elicit the desired value (e.g. Derived From Case, Current Path, User Input, Fixed Value, etc.) and complete the associated elements 3.
Click on Save. The new system action instance appears in the design area, ready for accurate positioning alongside other related building blocks within the task path workflow structure, together with the logical inter-related connections.
Click on Save.

Tip

1 Where only a small number of parameter values are not required, activate the All tick box first and then deselect individual items from the full list, as appropriate; the All tick box will be automatically removed once an item is deselected.

Note

1 System validation rules ensure that the name entered for each system action building block is unique for the version in current focus.

2 This option is only applicable to system actions that are triggered following end user qualification, and once logical connections (joins) have been established.

3 For instance, where Current Path is selected, the spy-glass icon is available to nominate the Task Information Fields or Form Fields integral to the workflow structure that will hold the required values.

System Action Method	Description
Launch Pop-up	A prescribed process, notification or data capture opportunity managed through a specific window can be triggered using the embedded system action.
URL	A website address pertinent to the progression of the overall task path workflow can be launched dynamically using the embedded system action.
Process	A discrete event pertinent to the objective of the task path workflow can be executed via the system action e.g. setting the automatic approval outcome for a rent review process.
Stored Procedure	Data processing algorithms defined externally within a SQL stored procedure can be executed on-the-fly using the embedded system action.
Web Service	The controlled sharing of common data sets with third party web applications can be initiated through the system action.
Create Linked Case	A CRM Case, Generic Case or Support Provision Case can be launched automatically at a specific point along the task path workflow, triggered by the system action.

See related topics...

Understanding the task path creator

To configure the workflow structure of a task path definition

To add a decision building block to a task path workflow

To add a delay building block to a task path workflow

To add a form building block to a task path workflow

To add a milestone building block to a task path workflow

To add an automatic completion building block to a task path workflow

To join building block components within a task path workflow