Exchanging Workspace Data
When multiple development environments share data for reuse or testing purposes, this can be represented as follows:
In this case, the goal of the data exchange is one of the following:
Sharing a “library” of reusable objects
Development Server A can be an environment focusing on “reusable” objects (or projects), and its modeling objects have to be retrieved by all other development servers.
- Synchronize when working on the same projects<br> Development Server A and B are working on the same projects but on different aspects. From time to time, they need to “synchronize” so that Development Server A can incorporate the changes from B and vice versa.
The typical process will be as follows:
- [In the source environment]
- For each workspace containing objects or projects that need to be given to another environment, create an export project.
- [Setup the export project]
- Make sure that you apply the necessary filters which will define the exact subset of data that you want to include in your export.
- [Using email or another manual means of data exchange]
- Give your export results to the people responsible for the destination environment.
- [In the destination environment]
- Make sure that the necessary workspaces exist up front, before uploading and importing the
received file.
Warning: The Designer does currently not support importing data in a different workspace.Reference: For more information about exporting workspace data, please refer to Managing Exports and Imports.
- Make sure that the necessary workspaces exist up front, before uploading and importing the
