Overview
You can export an application, packages or selected items from PhixFlow. This is useful when you want to:
- to take a back up of an application or a set of items on which you are working
- It's a good idea to do this regualrlyregularly, as PhixFlow has no undo.
- to import an application or package to another instance of PhixFlow.
For example, it is common to have a development instance in which you create applications. When the application is ready, you then export it and import it into a production instance to make it available to application users.
...
Drag items from the repository into the window then click either the Export or Copy button. _ there is no longer a copy option??
When you add an application to the export, PhixFlow asks if you want to also add packages that the application uses. We recommend you always include packages when you plan to import to another instance, as the import process reports errors if an item refers to something that isn't present in the new instance.
...
In addition to being able to export items ready for import to another instance, you can also copy items into the same instance using the copy option.
In PhixFlow, items are often associated with other items. For example, a stream is run by an analysis task or a style is used by a layout component. When making a copy, PhixFlow does not update associated items. The following table provides some examples:
Item copied | Associated items | What happens to associated items |
---|---|---|
StreamA is copied to streamB. | An analysis task runs streamA. | The analysis task is not changed and only runs streamA. |
Shared-style1 is copied to shared-style2. | There are 10 layout components that use shared-style1. | Shared-style2 has no components. The 10 layout components that use shared-style1 are not changed. |
...