To add a form building block to a task path workflow

The procedure to add a form 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 Form () building block to the design area. The Configure Form window is displayed.
Enter a Name for the new form instance into the field provided 1.
Choose the relevant Form using the corresponding spy-glass icon () i.e. the form template instance that will be launched as an output of the building block. The Search Form window is displayed, ready to locate the desired form template instance: (a) Enter a form definition name or choose an overarching entity type using the search fields provided and click on Search - All possible matches are returned in the Search Results summary table; (b) Double-click on the row matching the desired form template to be linked to the building block instance or use Refine Search to enter alternative criteria - The selected entry is displayed in the corresponding field.
Where completion of the form instance is Mandatory, activate the corresponding tick box provided.
To prevent the form instance from being relaunched for a reset task path, activate the Do not repeat tick box provided.
Where the form needs to be revisited at a predetermined frequency, activate the Recurrent task tick box provided.
Where the case owner user account is to be automatically assigned responsibility for completion of the form, activate the Allocate to case owner tick box provided.
Alternatively, using the Allocate to users and Allocate to roles drop-down fields, multi-select all desired user accounts and overarching roles to define a wider network of responsibility.
Using the SLA definition drop-down field, select an overarching target completion framework appropriate for the form building block.
Where the workflow structure has been defined as a Void Path, activate the Link start date to void date tick box provided, as appropriate, to indicate that the start date for the new form instance will match the commencement of the asset void episode 2. Use the adjacent Void date type drop-down field to steer the derivation of the commencement date i.e. Void Start Date or Count Back from Void Start Date (entering the Days before void start integer value to control the retrospective launch point).
Click on Confirm. The Recurrence Rules window is displayed, ready to define the frequency and duration over which the form should be revisited 3. This requisite step is covered separately in the topic To define recurrent rules for a task component building block. With all configuration steps completed, the new form 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.

Note

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

2 This option is restricted to those task path definitions that have been classified as a Generic Case and configured with the Void Path attribute.

3 This option is only activated in the instance where the Recurrent task attribute has been activated for the form building block.

See related topics...

Understanding the task path creator

To configure the workflow structure of a task path definition

To define recurrent rules for a task component building block

To add a communication building block to a task path workflow

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 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