-
A document and its files are published from the tool. The result of this publish is that a SmartPlant Foundation three-tier document (master/revision/version) is created in the DWShared domain in the project it was published to.
-
The associated files are stored at the tool schema version, which may not necessarily be the same as the SmartPlant Foundation schema version. A relationship to an object representing the SmartPlant schema is also created.
-
A workflow is set up to manage the process of getting the contents of the file loaded and then merged into an approved area. This workflow can optionally trigger off a load into a sub-configuration.
The user can log in to a particular configuration and view the documents that need approval.
Optional data load
This optional step in the workflow is used to load the data into a sub-configuration so that data can be approved. A Scheduler task is used so that the user does not need to wait for the operation to complete, as this may take some considerable time if it is a large file.
This task triggers a transform of the files if they are a different version to the current SmartPlant schema version loaded. Once the transform is complete, a sub configuration is then created, and the contents of the file can be loaded. At this stage, the data is unapproved.
Data approval
The user is able to see the data that needs to be approved in the workflow step and is able to change to that configuration. This can be done either from the main configuration selection dialog box or from a shortcut menu on the document.
Using standard SmartPlant Foundation functions, the user can navigate the data in the domain. The user can view that data using standard SmartPlant Foundation functionality such as the details form, the properties grid area, and ad hoc reporting as well as some of the navigation functions.
There is a new compare function that can be used to compare the data in the unapproved configuration with the project or plant configuration.
