In many cases Trimble Unity Construct workflow processes are connected and flow from one to another through the project life cycle. An example of this is a potential commitment item that becomes a request for information. Or perhaps a request for information later becomes a change order request, which is ultimately rolled into a change order along with other potential change orders. Creating lookup processes is very helpful, for instance to generate reports that show how workflow process instances are linked together. It may also be important for you to know if a change order is tied to a potential change order, and if that potential change order is linked to one or more RFIs. so that it is clear what led to the change order.
A third example of lookup processes in action would be if an RFI led to a potential change order, and if that potential change order was rolled into a change order, being able to see at a glance the big picture of the linkage among the processes, you can easily see the current disposition of the RFI within the big picture.
In Trimble Unity Construct, you link one process to another by using a data field of the type Lookup Process. The process will have been defined with a field titled Lookup Process. For such processes, a link will be displayed titled Lookup which allows you to select a non-draft instance of the linked process defined for the data field. This Lookup popup offers filters to facilitate searching on the instances.
For every primary process there is a list of all its dependent process data-field combinations, along with functionality so that you can directly add a new dependent process or attach an existing dependent process.
For detailed steps on setting up lookup processes, see Set up Lookup Processes.