×

Supercharge your Proficy solution! Download a free trial of Proficy Operations Hub, CSense analytics, and more. Explore our Proficy 2024 releases!

Home
Data Administration
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.
OPC Server Configurations
OPC servers, including all child groups and tags, can be exported and imported into different systems. The IDs will be consistent between the two systems, ensuring all data links continue to work.

Workflow IPI
Get Started
Tutorials
Orientation
Configure Your Environment
Security
Resource Information and Configuration
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.
    - General Configuration Transfer Considerations
      Certain considerations apply across multiple Workflow resource types when transferring configurations.
    - OPC Server Configurations
      OPC servers, including all child groups and tags, can be exported and imported into different systems. The IDs will be consistent between the two systems, ensuring all data links continue to work.
  - 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.
  - 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
Forms and User Displays
Building and Configuring Workflows
eSOP
ActiveX Task Controls
Service Interfaces
Operator Task List in the Workflow Client
Best Practices

OPC Server Configurations

OPC servers, including all child groups and tags, can be exported and imported into different systems. The IDs will be consistent between the two systems, ensuring all data links continue to work.

Possible Issues and Solutions

OPC Server with Same Name/Prog ID and Different ID

When an OPC server exists with the same name or Prog ID, but a different ID, the import will fail. The existing server must be deleted before importing the new one. By doing so, existing workflow call methods can lose bindings.

OPC Server with Same ID on Target System

When an OPC server with the same ID exists on the target system, changes, such as new groups and tags from the import are merged in. Nothing will be deleted from the target server.

OPC Server IDs on Two Separate Systems

Two separate systems with different OPC server IDs cannot import changes directly from one system to the other.

Deleting OPC Servers with Active Subscriptions

OPC servers cannot be deleted if there are active subscriptions to the data items. As a result, conditional events tied to OPC data must be disabled to allow the OPC server to be deleted, and then re-enabled after the OPC server has been imported.

Note: If you do not use Project to import OPC data, ensure OPC data is imported before importing workflows, equipment, and events.