Application package

Application package will be deprecated. That means the features are still available, but we do not recommend implementing if not already used.

Application Package is a way to package, license and lock specific solutions.

A package can contain workflows, package roles, package properties and portal tabs and can, if licensed, be used by users connected to user type FullUser and AppUser. If the package is unlicensed, it is available to FullUsers.

Package settings


Icons and Theme color: Select the icons and banner color for the package.

  • Name: The Name of the package

  • Application Package ID: The ID of the application package. This ID is when licensing the package.

  • Package Short Description: Enter the description for the package here

  • Create by User: The Flow ID of the user that created the package

  • Date Created: The date the package was created

  • Package Owner: Editable field into which the package owner can be entered. This is useful

  • Copyright: Editable field for copyright

  • Environment Origin: The name of the environment on which the package was originally created

  • Original Flow Version: The Flow version on which the package was originally created

  • Business Segment: Possible to set business segment for the package, drop down list

  • Process: Possible to set process for the package, drop down list


The connectors tab defines which connectors can be used in the package. The technical set up of a connector is still done in Environment - Connectors, the package only contains a mapping.

  • Name: The name of the connector. This name is what is seen in the connector drop down list when creating or moving workflows into the package.

  • Type: The type of connector. Value if fetched when mapping the connector.

  • Mapped name: Drop down list showing all connector available to be selected from. Once added, it is possible to change the mapped connector but only to connector of the same type.


The Roles tab shows the package access roles. The roles can be added, removed and edited. The roles structure is the same as in the rest of Flow, with a group ID and roles connected to the group.


Package specific properties are added removed and edited in the Properties tab. A package property is set up the same as in Environment - Properties but are only available within the package.

Portal Tabs

The portal tab shows the Flow Portal tabs connected to the package. Portal tabs can be added or removed. It is only possible to connect whole portal tabs to a package, not individual portlets.


Application package workflows are created the same way as normal with the difference that the available connectors are only the ones defined in the Package Settings - Connectors tab. Workflows can be dragged and dropped into a package, the user is then asked to map the connectors used in the workflow to the ones package settings.

A package can contain one or more menus. A package related menu is configured the same way as a non-package menu, ie workflows and inboxes can be added, and roles connected. The roles available for a package menu are the ones defined in package settings.

Workflows however, are not just limited to the ones in the package but all workflows can be added. An info message is displayed to notify the user if a workflow is not in the package - ?Add external workflow to package menu?, yes or no will either add the workflow or about the action. Package workflows can also be added in external Menus.


A package can contain folders in multiple levels. All workflows and menus in the folders will belong to the same package and have the same package settings data available.

Package Actions

Import and Export

A package can be exported and imported using the right mouse button options in the navigator.

  • Export: it is the that package content that is exported. External workflows connected to a menu will not be included in the export. All workflows in the package must be committed and published before the package can be exported.

  • Import: at import, the user will be asked to map all package connectors. If the package already exists, the user gets the options to replace the existing package or to create a new. New packages created will get a new package id. The rest of the metadata remains the same. If a new package is created and the original package contains portal tabs, the portal tabs are not duplicated but the mapping is to the same tabs as the original package.

Individual workflows are exported and imported outside the package.

The application package only contains connector mappings and not the full connector. Before importing into a new environment, it is recommended to check that all relevant connectors exist.


An application package can be locked by right mouse clicking on the package, selecting Lock. All workflows in a package must be committed before it can be locked. Any package content open in the studio will be closed when the package is locked.

If a package is locked it is not possible to open workflows or change metadata.

For a locked package the following is still editable:

  • Menu: add and remove workflows, inbox and category

  • Menu: add and remove package roles

  • Package settings - Connectors: possible to change the connector mapping to enable the customer to maintain connect settings themselves

A locked package is exported and imported as locked.

If importing into an environment where the package id already exists, the user will not get the option to create a new package but only the possibility to replace the existing one.

Forgotten password

It is possible to unlock the package for which the password has been forgotten. Contact support for assistance.

Last updated