Swimlane Solution Packages

use swimlane solution packages (ssps, file extension ssp ) to transfer collections of applications, applets, playbooks, builder components, builder solutions, and their associated entities between turbine instances at a glance task description link export an ssp package one or more entities and download as an ssp file export swimlane solution packages docid\ lke ku rdui2wkwcefj3w import an ssp upload an ssp or json file and selectively import entities into turbine import swimlane solution packages docid\ inud2c loasyyc1rptbrr repackage an ssp re compress an unzipped and edited ssp so it imports correctly repackage an unzipped ssp file docid\ yevfl9bcuypqfmozwrzft what an ssp contains an ssp packages the selected entity and all of its dependencies into a single file the following table shows what is included and what is excluded included excluded root application, applet, playbook, builder component, or builder solution application history and record history associated applications and applets records workflows for root and associated entities secure credentials and key store values (can be added after import) reports, workspaces, dashboards, and export templates secure values in asset configurations (can be reconfigured after import) playbooks (including parent and nested playbooks) connectors (maintain separately) orchestration tasks, ingestion rules, sensors, and correlation rules assets, plugins, and dynamic orchestration assets builder components, builder solutions, and builder intents mapped inputs to key store values (keys removed; add after import) export entry points you can export an ssp from any of these starting points entry point how to access application or applet from the applications and applets page, or from within application or applet builder playbook from the playbooks page or from within an open playbook builder component from the component context menu in the builder builder solution from the solution context menu in the builder global export from the applications and applets page, select multiple entities across types for a combined export selective entity export and import ssps include a relationship graph that maps dependencies between entities during export or import, turbine displays a tree of all entities in the package you can select or deselect individual entities dependent entities are auto selected and locked when their parent is selected ssps exported from older versions of turbine (before the relationship graph feature) do not support selective entity export or import all entities in those packages are included automatically same name, different identity in the target tenant if the target tenant already contains a playbook, builder component, or other packaged entity with the same name as an item in the ssp, but that existing copy came from another export (a different sharing identity ), the import may stop with explicit rename or save errors that behavior is by design so you can resolve the conflict deliberately for message examples and resolution options (rename in tenant, partial import, clean tenant), see import errors same name, different sharing id https //docs swimlane com/import swimlane solution packages#import errors same name different sharing id in import swimlane solution packages permissions exporting and importing ssps requires the system administrator role a system feature flag ( hidesspimportexport ) can hide the import and export ui if you do not see the import or export options, contact your administrator to verify the flag is not enabled