The Project Data flow type or business flow is used to transfer project data between two applications or between two distinct deployments of the same application. For example, to transfer project data from a P6 Testing environment to P6 production environment.
The flow step sequence in a project data business flow is organized as follows:
- Initialization
This step initializes the projects in the source application before the data is loaded into Gateway. It is available in Project Data flows and Migration Data flows for the following providers only:
- P6 EPPM
- Primavera Cloud
- Unifier
For single project jobs, the Initialization step displays as the first step.
For parent-child jobs, the Initialization step displays for the parent job because the projects need to be initialized before the number of child jobs is determined. It is the only step displayed for the parent job. This step is not displayed for any child jobs. The start and end times of each step is stored in GMT and displays as per your local time.
- Notes:
- “Baseline” Requests / Responses can be suffixed with a number which corresponds to the baselines selected in the relevant parameter. Numbering starts with: 0, 1, 2, 3, etc.
- Primavera Cloud has a hard limit which can cause multiple Request / Responses suffixed with a number. Numbering starts with 1, 2, 3, etc.
The step will only display when the Project Filter within the Business Flow / Synchronization uses an option other than Lookup In <product>.
- Load from Source: This step loads the project data from the source application into the Gateway framework so that it can be processed.
- Convert from Source to Gateway Format: This step converts the source project data from the source format to the Gateway format.
- (Optional) Load from Destination: This step loads the project data from the destination application into the Gateway framework so that it can be processed.
- (Optional) Convert from Destination to Gateway Format: This step converts the destination project data to the Gateway format.
- (Optional) Compare Project Data: This step compares the converted source Gateway data with the destination Gateway data. This step compares each object and uses the following rules to determine how the data is synchronized in the Update Destination step.
- If the data is in the source object but not in the destination object, the data is created in the destination object during the Update Destination step.
- If the data is in the destination object but not in the source node, the system performs the following steps:
* Inspects the cross reference tables to determine whether the data has ever been synchronized.
* Determines whether the Delete parameter has been set for the flow.
If the data is in the cross-reference tables and the delete parameter has been set for the flow, the data is deleted from the destination during the Update Destination step. Otherwise, the data is not deleted in the Update Destination step.
- Objects that contain updated data are marked for synchronization.
- Objects that contain the same data in both the source and the destination nodes are ignored.
- Convert to Destination Format: This step converts the project data from Gateway format to the destination format.
- (Optional) Review data: This step enables you to review the source data before updating the data in the destination application.
- Update Destination: This step saves the project data into the destination application's database.