Export Swimlane Solution Packages

export swimlane solution packages (ssps, file extension ssp ) to transfer playbooks, applications, applets, builder components, builder solutions, and their dependencies to another turbine instance or to the content library exporting ssps requires the system administrator role what is included in an export 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 (add after import) reports, workspaces, dashboards, and export templates secure values in asset configurations (reconfigure 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 back after import) export an application or applet ssp you can start an export from the applications and applets main page or from within the builder export from the applications and applets page open the applications and applets page click the plus icon and select import or export a package select the export radio button turbine loads the available entities select the check box next to each entity you want to include click export turbine validates the selected entities and displays a preview of the package contents if no errors are detected, click export to download the ssp file if there are potential issues, click continue export to proceed or resolve the issues first see docid 2yrtroy1worc59vumpste export from within application or applet builder open the application or applet in the builder click the ellipsis icon in the taskbar menu select export application or export applet turbine displays a preview of the entity and all associated content that will be packaged review any potential issues if no issues exist, click export if issues are found, click continue export to proceed anyway, or click go to application to fix errors first when you select one application or applet, the export packages all associated content (workflows, reports, assets, playbooks, and so on) as a single solution review the entity tree to confirm what is included export a playbook ssp navigate to orchestration , then playbooks find the playbook you want to export click the ellipsis icon and select export turbine displays a preview review and click export to download you can also export from within an open playbook by clicking the ellipsis icon in the playbook taskbar and selecting export if the playbook has parent or nested playbooks, they are included in the export automatically export a builder component or solution ssp navigate to the builder component or builder solution you want to export click the ellipsis icon or context menu for the entity select export turbine displays the entity tree dependent components and their playbook flows are auto selected and locked review the selection and click export to download the ssp file when you export a builder solution, all associated builder components and their playbook flows are included and cannot be deselected this ensures the solution remains functional after import export a global ssp use global export to package multiple applications, applets, builder components, builder solutions, and playbooks into a single ssp open the applications and applets page click the plus icon and select import or export a package select the export radio button select the check boxes next to all entities you want to include across any combination of types click export selection file name multiple entities or all entities swimlane global export package ssp a single entity uses that entity's name (for example, my application ssp ) select and deselect entities during export, turbine displays a tree view of all entities and their dependencies based on the relationship graph the tree shows each entity with its type (application, playbook, component, and so on) and any child entities nested beneath it you can select or deselect individual entities by clicking their check box select all or deselect all using the bulk toggle at the top of the list view auto selected dependent entities, which appear with a locked check box and cannot be deselected independently dependency auto selection rules when you select turbine also selects a builder solution all child builder components and their playbook flows (locked) a builder component all nested builder components it depends on (locked) a playbook all connectors referenced by the playbook a parent entity all child entities beneath it for applet exports, entity selection is not available the entire applet and its dependencies are always exported review export results after validation or after the export completes, turbine displays a results screen with up to three tabs tab contents take action actionable issues you can resolve inline a yellow badge shows the count take note non actionable informational warnings that do not block the export export inventory a read only tree of all entities included in the exported package actionable vs non actionable issues category description example actionable issues that require your attention before the export is fully functional on import a secure credential was removed; a key store reference was stripped non actionable informational warnings the export can proceed a referenced entity outside the package is missing; a dependent entity was not selected common error types error meaning resolution credential removed a secure credential was stripped during export reconfigure the credential after import missing reference a referenced entity is not included in the package add the missing entity to the export selection, or accept the warning plugin version mismatch the target system has a different plugin version upgrade or downgrade the plugin on the target system incompatible swimlane version the ssp requires a newer turbine version upgrade the target turbine instance dangling reference an entity references a playbook, sensor, or asset that no longer exists use perform cleanup and retry to remove the broken reference and re validate disabled playbook a playbook was disabled as part of the export the playbook can be enabled after import disabled sensor a sensor (webhook) was disabled as part of the export the sensor can be enabled after import use cleanup and retry if the export detects dangling references (orphaned playbooks, sensors, orchestration tasks, or components), a perform cleanup and retry button appears in the footer click perform cleanup and retry turbine removes the broken references from the source system turbine re validates the export automatically review the updated results cleanup modifies the source system by removing orphaned references this action cannot be undone copy or download export notes from the results screen, you can save a summary of all issues and warnings click copy notes to copy the summary to your clipboard click download notes to save it as a txt file navigate to the source entity if errors prevent the export, the footer displays a navigation button based on the entity type entity type button application go to application applet go to applet playbook go to playbook click the button to open the entity in the builder, resolve the errors, and retry the export publish to content library if your turbine instance is connected to a content library , you can publish an ssp directly instead of downloading it the publish wizard guides you through a multi step process step 1 content information choose how to publish option description publish as new content (v1) creates a new entry in the content library enter a name and optional description the version is set to 1 0 0 publish as a new version of existing content (v1+) updates an existing content library entry select the existing package from a table showing name, current version, and last modified date enter a new version number step 2 package content turbine displays the entity tree select or deselect entities the same way as a standard export step 3 review changes turbine validates the package and displays any potential issues review actionable and non actionable issues you can resolve issues now or continue publishing step 4 summary review the final publish details name and version of the content commit message describing the changes click publish to push the ssp to the content library resolve merge conflicts if the content library detects a conflict between your local content and the remote repository, turbine displays a merge conflict screen for each conflicting ssp, you see two options option description keep local changes overwrites the remote version with your local version shows who last published and when keep remote changes discards your local version and keeps the remote version shows who last published and when select your resolution for each conflicting ssp click apply to resolve the conflicts if new conflicts arise after resolution, repeat the process handle sync errors if the publish succeeds locally but fails to sync to the remote repository, turbine displays an error unable to connect to your remote repository content has been published to your local content library, but the sync to your remote repository failed to resolve wait a few minutes and retry if the error persists, manually push the changes from the local content library contact support if the issue continues next steps