At some point in the process, the data needs to be loaded into the correct configuration. Because the approval steps are optional, the starting point of the load is from the published document, rather than from the loaded unapproved area.
This means that data approval needs to be carried out again if the optional load was performed, but it also means that there is just one route by which data can be loaded into the configuration.
This task can take several minutes or hours to complete, so the Scheduler is used. Like the optional SmartPlant integration load, the process of loading the data to the published domain can be initiated from:
-
A process step that queues the load-to-configuration in the Scheduler.
-
A manual step in case the document is not added to a workflow.
-
From the document again if the process fails.
Two processes take place when loading data; a load process that populates the tool specific publish domain, and the consolidate process that creates a shared object and relates the published data to the object.
Initially when an object is consolidated there is just one reference from the shared object to a published object. But as downstream applications begin to take that object and add additional information, and the data is published and loaded into other domains, the shared object will begin to point to multiple objects. When the document object contained in the data file is loaded, rather than creating a shared object, a link to the published document is established.