In public works, it's common that one work assignment leads to another. Sometimes the follow-up work is expected: For example, the Sewer Department might know that each time it flushes a sewer line, it has to conduct a follow-up water test two weeks later. At other times, the secondary task might be unforeseen, such as when a street sweeper notices a portion of a curb must be repaired. Lucity's Resulting Tasks function makes it easy to initiate and track either type of workflow.
How it works
Resulting Tasks can be added to a Work Order in two ways:
Automatically, through Task Setup - You can configure the Task Setup record for the primary task to include a Resulting Task. Then, when any user adds the primary task to a Work Order as its Main Task, Lucity copies the Resulting Task to the Work Order, as well. This method is an efficient way to configure jobs that almost always require a particular follow-up task. More information about Task Setup and Resulting Tasks
Manually, through the Work Order - Click the Add Record button in a Work Order's Resulting Task grid to add a record directly to the Work Order. This method is convenient when a worker performing one task notices the need for another type of work.
With either method, when you create a Resulting Task, you also should consider how you want to create the Resulting Work Order. There are two options:
Let Lucity generate the resulting Work Order automatically - Check the Create WO Flag on the Task Setup > Resulting Task record or enablethe Automatically create Work Order using End Date option on the Work Order > Resulting Task record. Then, after the primary Work Order is closed, Lucity will generate the Resulting Work Order on the date you specify (through the Frequency and Occurrence Interval fields).
Manually generate the Resulting Work Orderyourself - Run the Create Resulting Work Order | Selected Record toolkit to generate the Resulting Work Order when the timing is right for you.
Scheduling Options
The configuration of the Resulting Task's scheduling fields and the method used to trigger the resulting Work Order determine the Start Date of the resulting Work Order. The following chart explains how the available timing options and triggering methods work in combination to determine the Start Date of a resulting Work Order.
Frequency / Occurrence Interval
Start Date / Time
Work Order Generation Method
Resulting Work Start Date/Time =
Scenario 1
Automatic*
Original Work Order's End Date + (Frequency x number of days in Occurrence Interval)
Scenario 2
Manual (Toolkit)
Current date
Scenario 3
Automatic*
Start Date set on the Resulting Task record
Scenario 4
Manual (Toolkit)
Start Date set on the Resulting Task record
Scenario 5
Automatic*
Start Date set on the Resulting Task record
Scenario 6
Manual (Toolkit)
Start Date set on the Resulting Task record
Scenario 7
Automatic*
Original Work Order's End Date
Scenario 8
Manual (Toolkit)
Current date
*In order for Lucity to generate a Work Order automatically from a Resulting Task, the Resulting Task child record must have the Automatically Complete Work Order using End Date option enabled.
