Changes
After selecting an import job a file picker will open in order for the user to select an excel file that contains information corresponding to the import type that was selected. This excel file will be saved in the database as an EXCEL_IMPORT_DOCUMENT. The import job will read the data out of this excel and create corresponding proxies. To create real objects out of the proxies the Apply Imported Data Job must be executed. This means the user can first import all the needed data by using the different import jobs and after these jobs have created all the proxies for the data the user can execute the Apply Imported Data Job.
=== Import All Users From Source Project ===
Reassembles the JSON property of all commissioning tasks that are operation-based tasks (precom/hatoco/qchook). Contains general information needed by the client.
=== Export Documents ===
The Export Documents Job exports all ExecutionDocuments, PunchPointAttachments, ScopeChangeAttachments, and Timesheets from a Turnaround Project. The job automatically organizes these documents into a structured folder hierarchy based on properties of the project and each document.<br>
Folder Structure:<br>
If any relevant property is missing or empty, the folder will be named UNKNOWN. Any invalid characters are replaced with an underscore. <br>
* Level 1 – Project Name
* Level 2 – Document Type:
* EX_DOCS for ExecutionDocuments
* SC_DOCS for ScopeChangeAttachments
* PP_DOCS for PunchPointAttachments
* TS_DOCS for Timesheets
* In cases where the generated full path exceeds Windows limits, the export falls back to a simpler structure by creating a folder named TooLong at this level.
* Level 3 – Plant Section Name
* Level 4 – Equipment Group Name
* Level 5 – Equipment Type Name:
* Level 6 – Tag Number or Functional Location:
* If a tag number is provided, it is used as the folder name; otherwise, the functional location name is used.
== Job for WorkOrder instance ==
