When Primavera Cloud is the source provider in a master data flow, there are no parameters to set for the delivered business flows.
- 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.
- Primavera Cloud Calendar Filter
Use this setting to identify and select Global Calendar values in Primavera Cloud using Name or WorkspaceId. Enter multiple values as comma-separated values. Select Add row to enter multiple filter criteria for selecting global calendars. Select Edit row to change a current filter criteria or value for selecting a global calendar.
- Primavera Cloud Role Filter
Use this setting to select roles in Primavera Cloud using RoleId or WorkspaceId. Select Add Row to enter multiple filter criteria for selecting roles. Select Edit Row to change the current filter criteria or value for selecting roles in Primavera Cloud.
- Primavera Cloud Resource Filter
Use this setting to select resources in Primavera Cloud using RoleId or WorkspaceId. Select Add Row to enter multiple filter criteria for selecting resources. Select Edit Row to change the current filter criteria or value for selecting resources in Primavera Cloud.
- Primavera Cloud UDF Type Filter
Use this setting to select and transfer the following Primavera Cloud UDF Types: Activity, Project, Resource Assignment, and WBS.
- Primavera Cloud UDF By Workspace Filter
Use this setting to select UDFs associated with a specific workspace in Primavera Cloud by using WorkspaceId. Select Add Row to enter multiple filter criteria for selecting UDF types. Select Edit Row to change the current filter criteria or value for selecting UDF Types in Primavera Cloud.
When Primavera Cloud is the destination provider in a master data business flow, set values and attributes for the following parameters
- 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. This information is used in the Load and Save steps of the flow.
- 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.
- Provide email notification for selected job status
This parameter displays only when you have specified an Email Address in the Mail Configuration tab of the Gateway Settings page.
Use this setting to enter email IDs of individuals who would need to be notified when synchronization jobs are completed with any of the following job statuses on the Monitoring page: Completed, Review, Cancelled, Completed with Errors, Completed with Warnings, or Failed.
Select the Attach Data Details for Job check box to include details of the data transfer in the email.
- 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.