Configuration Export is the way that applications and miscellaneous configuration components are exported from PhixFlow. You may want to export your configuration for a number of reasons - e.g. to back up an application, or set of configuration components, you are working on; or so that you can import it somewhere else.
...
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.When making a copy, PhixFlow considers whether items would be expected to have multiple associations. For example, a copy of a layout component will include its shared style. This is because a shared style is expected to occur in many layout components. However, a copy of a task plan that contains an analysis task will not contain any streams. This is because a stream is expected to be run by only one analysis task
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. |