Copying Workflow Setups from Other Schemas

You are here: Primavera Unifier Administration Mode > Business Process Setup > Setting up Business Processes > Copying Workflow Setups from Other Schemas

Copying Workflow Setups from Other Schemas

Some workflows can encompass many steps, as well as conditional routing and sub-workflows. Most of your time as administrator can be spent setting up the workflow schemas in your company. To make setting up workflow schemas easier and faster, Primavera Unifier provides you the option of copying existing setups from other workflow schemas.

For example, if you have set up a large schema for an approval process that includes separate workflows for different provisos, you can copy the setup of one schema to another workflow, and make incidental changes where necessary, rather than set up the entire workflow schema again.

Or, if you have a complex schema for setting up a project or shell, you can copy that schema to set up a different project or shell in your same Primavera Unifier environment.

You can copy a setup from here:	To here:
A business process in the Company Workspace	The same business process in the same Company Workspace If any users, groups, or SmartForms are defined in the setup, they will be copied over if they do not already exist; matching will be done on the name.
A project template for a business process	Another project template for the same business process If any users, groups, or SmartForms are defined in the setup, they will be copied over if they do not already exist; matching will be done on the name.
A business process in a project	A project template for the same business process If any users, groups, or SmartForms are defined in the setup, they will be copied over if they do not already exist; matching will be done on the name.
A shell template for a business process	Another shell template (of any shell type) for the same business process If any users, groups, or SmartForms are defined in the setup, they will be copied over if they do not already exist; matching will be done on the name.
A business process in a shell	A shell template (of any shell type) for the same business process If any users, groups, or SmartForms are defined in the setup, they will be copied over if they do not already exist; matching will be done on the name.

Business Processes Must Match

In all cases, the business process name, type, sub-type, classification, studio owner, and version number must match or the copy function will fail.

About the version number

The number in the Version column of the business process log shows the Primavera uDesigner version number. This number represents the number of times the design has been changed from Draft mode to Complete. Primavera uDesigner automatically increments the version number whenever a design is returned to Draft mode. When the draft is changed to Complete, it shows that number. This version of the design in Primavera uDesigner may or may not be the version that is active in Primavera Unifier. The version number that appears on this log in Primavera Unifier shows the last design version that was imported. This number may not match the version number Primavera uDesigner, but it is the last active version of the design in Primavera Unifier. The version number of the BP you are copying from must match the version number of the BP you are copying into.

At the Company Level, Copy a Setup from Another Setup in the Same BP

Copy a Setup from One Project/Shell Template to Another

Copy a Setup from a Project/Shell to a Template

Oracle Corporation