×

Have You Seen Workflow Lately? Click here to check out all the new features in the latest version.

Supercharge your GE solution! Download a free trial of Proficy Operations Hub, CSense analytics, and more. Learn more about the Proficy 2024 releases, by signing up for one of our upcoming events.

Home
Data Administration
Transferring Workflow
Transferring Different Types of Configurations Together
You can use projects to combine configurations for various Workflow resource types in a single package for transfer between servers or operational environments.

Workflow Products Documentation

Data Administration
- Data Administration Introduction
- Electronic Signatures and Audit Trails
- Data Sources
- Archives
- Custom Property Types
- Transferring Workflow
  - Transferring Workflow Configurations
    You can transfer configurations for Workflow resources between servers or operational environments by way of either export/import or projects.
  - Transferring Different Types of Configurations Together
    You can use projects to combine configurations for various Workflow resource types in a single package for transfer between servers or operational environments.
    - Combine resource configurations in a project
      The first step in transferring varying types of resource configurations together is to create a project, and then add the configurations to it.
    - Package a project to export its contents
      After you have created a project and populated it with resources, you must package the project as the next step in transferring the related configurations. When you package a project, a compressed file containing the related configurations is exported to a location that you designate.
    - Deploy a project to import its contents
      After a project has been packaged, you must deploy the resulting project file as the final step in transferring the configurations it contains.
    - Change project attributes or contents
      You can update a project by adding or removing Workflow resource configurations and/or modifying project attribute values.
    - Delete a project
      If a project is no longer relevant to your operations, you can delete it.
    - Project Editing and Packaging Display Details
      The Project Editor allows you to populate projects with differing types of resource configurations and then export the results in preparation for transfer to another system.
    - Project Deployment Display Details
      The Project Deployment display allows you to open a project file and deploy the resource configurations it contains to the current system. The display shows the contents of the select project file, information about the file's origin, and notes about the project currently deployed on the system (if applicable).
  - Transferring Configurations by Resource Type
    Using export/import, you can create files that contain configurations for Workflow resources of a given type or category for transfer between servers or operational environments.
  - Equipment Provisioning
    Workflow provides an efficient and effective way to import large amounts of equipment data using your SQL Server.
- Reporting

Transferring Different Types of Configurations Together

You can use projects to combine configurations for various Workflow resource types in a single package for transfer between servers or operational environments.

A project provides the means of transferring entire applications at once. The first time you do so, the project configuration and the resource configurations in the project are imported to the destination system. As an application evolves, you can change the project configuration on the source system, and then redeploy the project to the destination system. In this case, the transfer is handled as follows:

The pre-existing project configuration on the destination system is replaced with the modified project configuration.
The pre-existing resource configurations on the destination system are updated to reflect their counterparts in the modified project. For more information, see configuration updates in: General Configuration Transfer Considerations.
Any previously transferred resource configurations that are not included in the modified project are left intact on the destination system.

If you expect to update and redeploy projects over time, it is important to closely monitor project versions. The protocol used to track project iterations is major.minor.build.revision. Of these components, major and minor are user-specified, whereas build and revision are system-controlled. The build number increases by 1 each time a project is packaged, and the revision number increases by 1 with each change to project composition and each time an updated project is saved. Before redeploying an updated project, you should carefully review the contents of the project file, the information about the file's origin, and the notes about the project currently deployed on the system, as displayed in the deployment interface. These measures are especially important to ensure that you are deploying the intended version of the project.

For more information on the types of resources that you can transfer configurations for, see Content-Specific Transfer Considerations.

Note: If you want to transfer one or more files that contain configurations for only a single type of resource, you can export/import instead.