To add a communication building block to a task path workflow

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

1. 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.
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.
3. Using the standard 'drag and drop' technique, transfer a new Communication () building block to the design area. The Configure Communication window is displayed.
4. Enter a Name for the new communication instance into the field provided 1.
5. Choose the relevant Communication definition using the corresponding spy-glass icon () i.e. the communication template that will be generated as an output of the building block. The Communication Search window is displayed, ready to locate the desired communication: (a) Enter a communication name into the dynamic search field provided - All possible matches are returned in the Search Results summary table 2; (b) Double-click on the row matching the desired communication to be linked to the building block instance - The selected entry is displayed in the corresponding field.
6. Where the communication can be generated without end user qualification, activate the Run automatically tick box provided. Otherwise, select the desired communication 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.
7. Where generation of the communication is Mandatory, activate the corresponding tick box provided.
8. To prevent the communication from being regenerated for a reset task path, activate the Do not repeat tick box provided.
9. Where the communication needs to be repeated at a predetermined frequency, activate the Recurrent task tick box provided.
10. Using the SLA definition drop-down field, select an overarching target completion framework appropriate for the communication building block, and specify the associated reference point using the adjacent Calculate SLA from field i.e. Milestone Date or Task Start Date. Where Milestone Date is chosen, use the additional Milestone field to select an existing milestone from within the workflow path.
11. 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 communication instance will match the commencement of the asset void episode 3. 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).
12. 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 4.
13. Click on Confirm. The Recurrence Rules window is displayed, ready to define the frequency and duration over which the communication should be repeated 5. 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 communication 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.
14. 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 communication building block is unique for the version in current focus.

2 The field will operate as a dynamic search function and match against any element of the communication name, based on the successive characters entered; the result set is restricted to those communications linked to an entity matching the module classification of the task path definition.

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

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

5 This option is only activated in the instance where the Recurrent task attribute has been activated for the communication 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 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