Based on the role of MSP and Primavera Cloud providers and the data to be transferred in the business flow the following provider-specific parameters will display as either source or destination application parameters in the Business Flow wizard.
Users having the role of a Gateway administrator or Gateway developer can access and view all the parameters listed below. Set the behavior of these parameters in the business flow by specifying the Attribute for each as any of the following values: Hidden, Optional, Read-only, or Required.
Notes:
- Data identified by each parameter is processed by a flow step of the business flow. For more information on flow steps, see Appendix A: About Flow Steps.
- All values specified in the filter parameters will be used in the Load step of the flow for loading data from the providers designated as the source or the destination.
MSP Provider Application Parameters
When Microsoft Project is the source application, set values and attributes for the following parameters while adding or editing a project data business flow:
- MSP File to Upload
Browse and select the Microsoft Project file to be used by the business flow. This option is enabled only if you chose to set up an MSP deployment with the File Upload option in the Deployments tab of the Configuration page.
- MSP File Name
Enter the Microsoft Project file name to be uploaded by the business flow. This option is enabled only if you chose to set up an MSP deployment with FilePath or FTPService options in the Deployments tab of the Configuration page. This information is used in the Load step of the flow.
When Microsoft Project is the destination application, set values and attributes for the following parameters while adding or editing a project data business flow:
- File Name
Enter the file name that is to be used to download the data by the MSP provider.
- MSP File Version
Select the Microsoft Project version that the MSP provider will use to download the data.
- Synchronize one project at a time
A synchronization job is usually split into multiple child jobs with each child job transferring data in each project. By default all child jobs are executed simultaneously. Use this setting to determine whether to synchronize data one project at a time.
- Delete data that no longer exists in the source application?
Use this setting to determine whether data that no longer exists in the source application is to be deleted in the destination application. This parameter must be used in conjunction with the Compare flag selected in the Business Flow wizard.
Note: When you run a project data flow, it will delete only project level data in a business flow, but not the master data. This will prevent you from deleting master data elements such as resources, roles etc., that may be used in another project. However, if used in a master data flow, it will delete all relevant objects and fields.
- Only delete data that has been linked previously with the source application?
To use this parameter, you must also select the parameter, Delete data that no longer exists in the source application? During a synchronization, when the data is compared between the source and the destination application, data that has been added only in the destination application will not be deleted. However, if you deleted source data that was previously synced in the destination application, it will also be deleted from the destination application.
- Partition data to child jobs for large data transfers?
Use this setting if you are integrating large data sets between projects and between applications when P6 EPPM or Oracle Primavera Cloudis the source application. This parameter partitions large data sets logically into multiple child jobs.
- Child job object limit for partitioned data
Use this setting in conjunction with the Partition Data into Child Jobs? parameter. Enter a limit on the number of objects that can be included in the child jobs in the range 50 - 5000. Zero (0) is the default value.
Primavera Cloud Provider Application Parameters
When Primavera Cloud is the source application, set values and attributes for the following parameters while adding or editing a project data business flow:
- Primavera Cloud Project Filter
Use this setting to identify and select projects in Primavera Cloud using Project Ids, Workspace Ids, Project Code Type Name, Project Code Value, or Project Status.
Select Add Row to enter multiple filter criteria for selecting projects.
Select Edit Row to change the current filter criteria or value for selecting a project.
Select Delete Row to delete a filter criteria.
When Primavera Cloud is the destination application, set values and attributes for the following parameters while adding or editing a project data business flow:
- Workspace Location
Use this setting to specify the default workspace and populate it in a synchronization. If the value is set in Primavera Gateway, then Primavera Cloud will check if the Primavera Cloud Workspace field value exists and will use it to create the project.
P6 must send all global data assigned to the project with the project flow and all of that global data must be assigned to the workspace to determine where the project will be created in Primavera Cloud.
- Primavera Cloud Location Filter
Use this setting to specify location values in Primavera Cloud using CountryCode or WorkspaceId. Select Add Row to enter multiple filter criteria for selecting location values. Select Edit row to change a current filter criteria or value for selecting a location.
- Save data to Primavera Cloud if there are errors?
Use this setting to determine how data is to be processed when a job fails in Gateway. Select this option if you want to save the data in Primavera Cloud when a synchronization job fails in Gateway. Otherwise, deselect this option to ensure data is not saved in Primavera Cloud for failed jobs.
- Synchronize one project at a time
A synchronization job is usually split into multiple child jobs with each child job transferring data in each project. By default all child jobs are executed simultaneously. Use this setting to determine whether to synchronize data one project at a time.
- Delete data that no longer exists in the source application?
Use this setting to determine whether data that no longer exists in the source application is to be deleted in the destination application. This parameter must be used in conjunction with the Compare flag selected in the Business Flow wizard.
Note: When you run a project data flow, it will delete only project level data in a business flow, but not the master data. This will prevent you from deleting master data elements such as resources, roles etc., that may be used in another project. However, if used in a master data flow, it will delete all relevant objects and fields.
- Only delete data that has been linked previously with the source application?
To use this parameter, you must also select the parameter, Delete data that no longer exists in the source application? During a synchronization, when the data is compared between the source and the destination application, data that has been added only in the destination application will not be deleted. However, if you deleted source data that was previously synced in the destination application, it will also be deleted from the destination application.
- Partition data to child jobs for large data transfers?
Use this setting if you are integrating large data sets between projects and between applications when P6 EPPM or Oracle Primavera Cloudis the source application. This parameter partitions large data sets logically into multiple child jobs.
- Child job object limit for partitioned data
Use this setting in conjunction with the Partition Data into Child Jobs? parameter. Enter a limit on the number of objects that can be included in the child jobs in the range 50 - 5000. Zero (0) is the default value.