A package allows you to group configuration objects. Applications can have a number of packages, and packages can belong to a number of applications. Typically, packages are used to group configuration objects which form a "back end" component of an application, or a number of applications. These can then be shared across these applications. This page is for application designers who want to share PhixFlow items and layout components across multiple applications.
Overview
If you are designing multiple applications, you are likely to have a set of items that you want to use in all your applications. Items can include:
- analysis models and modelling objects
- streams and steam data
- dashboards and layout components
- images and styles.
You can group together the items that you want to share in a package. When is created, different applications can use it. You can also group items into multiple packages as applications can use several packages. Packages may be used to group objects required by a number of applications.
We supply the Theme 1 and Theme 2 palettes as packages. To import Theme 1 and Theme 2 to your instances, see Installing Packages. You can use the theme in any application; see About Themes.
Moving Packages Between Instances
You can export packages and then import them to another instance of PhixFlow. If you export an application, you must also export the packages it uses.
The import process compares the contents of the import with the items that are present on the target instance.
- If an item is not present on the target system and is present in the import, the new item is created on the target system.
- If an item is present on the target system and in the import, PhixFlow replaces the item on the target system.
- If an item is present on the target system but is not present in the import, PhixFlow permanently deletes the item on the target system. This includes streams and stream set data.
| Note |
|---|
If you have moved an item from an application to a package, remember to export/import the application and package together. The item is deleted from the application and added to the package. If you do not export/import the package, the item is deleted from the application and is no longer available. This also deletes references, so adding the package at a later date will not reinstate the reference between the application and the item. To reinstate the deleted object and references to it, export/import the application and the package together. |
Package Properties
The following fields are configured for Packages:Insert excerpt _standard_settings _standard_settings nopanel true
| Field | Description |
|---|---|
| Basic Settings | |
| Name | The name of the package. |
| Version | The version of the package. |
| Applications | |
| A list of applications linked to the package. Drag applications from the repository browser into the list to add them. | |
...