Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

PhixFlow provides for copying models and modelling objects, both internally, in the current PhixFlow instance, and externally (via export), to another PhixFlow Instance.

Copy

There are a number of ways of copying models and modelling objects within a single instance of PhixFlow.

  • Open a model and select Save a copy of the model layout. This will copy the analysis model but will not create a copy of the objects included in the model.
  • Open any model and select the objects to copy. Right-click on the model canvas (not on the selected objects) and select Copy Selected Objects.
  • Right-click on any individual object and select Copy object from the menu.
  • Drag the objects you want to copy to the Export Configuration and click on the copy button .

When you copy objects from a model, the following objects are created :

  • A copy of each object.
  • Input pipes into the copied objects from objects that the originals were connected to. Output pipes from copied objects are not copied unless the pipe is an input for another copied object.

See also Copying or Moving Table Data.

Export

There are a two options for exporting objects for import into another instance of PhixFlow.

  • Drag and drop the objects you want to copy to the Export Pane and click on the  button.
  • Click the  Administration menu and select Export Full Configuration. This will export the full configuration for the PhixFlow instance.

When you export objects of a model the export creates :

  • A copy of the objects you selected.
  • A copy of the pipes linking those objects.

When an object is imported which is already in the target instance (for example, if you have exported some objects, made some changes and now want to bring your changes back into your original) the import will update the objects already in the target instance.

If an application is imported which already exists in the target system, anything which does not exist in the imported version of the application will be permanently deleted.

Exports and Passwords

PhixFlow never exports passwords that are stored in items, such as . You must configure the passwords for the target instance.

If a password is provided during the file download process then all exported data will be encrypted. If no password is provided and your export password policy allows a blank password then all data will be unencrypted. If no password is provided and your export password policy requires a password, the download will fail. On import the password must be correctly entered to import the encrypted data. If the password is incorrect or not provided then no data will be imported.

Protect on Import

When you have several instances of PhixFlow, for example development and production instances, you may want some item properties to be different for each instance. Usually, when you export from a source instance, then import to a target instance, PhixFlow overwrites item properties with those from the source instance. To prevent the item being updated or deleted, in the target instance, tick the Protect on Import or Protect during import property, which is available for:

For the following items, you can protect data using specific properties:

  • No labels