PhixFlow provides for copying models and modelling objects, both internally, in the current PhixFlow instance, and externally (via export), to another PhixFlow Instance.
...
| Info |
|---|
| 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 in the following itemsfor:
- Datasource and Datasource instances.
- HTTP Datasource
- File Exporter
- Filter
- Email Account
For the following items, you can protect specific properties:
- File Collector → File Password - Fiona-todo check implementation - its not yet in the docs
- File Exporter → Recipient Expressions
- Task Plans properties: Enabled, Scheduled, Suspend on Failure, Suspended and Schedule.