The procedure to add a delay 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 Delay (
) building block to the design area. The Configure Delay window is displayed.
- Enter a Name for the new delay instance into the field provided
1.
- Using the Delay type drop-down field, select a parameter value to control the method by which the delay period is defined i.e. Conditional or Time.
- Where a Conditional delay is selected, click on Define Condition. The Statement Builder window is displayed, ready to compile one or more conditions to control the delay activation rules within the building block. This requisite step is covered separately in the topic Understanding the advanced statement builder. An overarching threshold limit can be defined using the complementary fields Maximum delay unit (Minutes, Days, Weeks, Months) and Maximum delay period (the unit multiplier 2).
- Otherwise, where a Conditional delay is selected, activate the Use advanced query tick box provided to indicate that a bespoke SQL stored procedure will be employed to execute more complex expressions; enter the Stored procedure name into the adjacent field 3. Again, an overarching threshold limit can be defined using the complementary fields Maximum delay unit (Minutes, Days, Weeks, Months) and Maximum delay period (the unit multiplier).
- Alternatively, where a Time delay is chosen, select the Calendar that reflects the required period structure for the delay using the corresponding drop-down field. The additional Delay unit and Delay period fields are provided to capture the appropriate frequency parameter (Minutes, Days, Weeks, Months) and duration multiplier (an integer) respectively 4.
- Where the delay instance is Mandatory, activate the tick box provided.
- 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 delay instance will match the commencement of the asset void episode 5. 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 new delay 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 delay building block is unique for the version in current focus.
2 The Up and Down arrows are available to increment or decrement the value, as required.
3 Where a stored procedure has been specified, a criteria statement cannot also be defined, and vice versa.
4 By way of example, if a delay of 5 days duration was required, a Delay period of '5' would be inserted, coinciding with a Delay unit of 'Days'.
5 This option is restricted to those task path definitions that have been classified as a Generic Case and configured with the Void Path attribute.
See related topics...
Understanding the task path creator
To configure the workflow structure of a task path definition
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 add a communication building block to a task path workflow
To join building block components within a task path workflow
Understanding the advanced statement builder
