Export Swimlane Solution Packages

export swimlane solution packages (ssps, file extention ssp) to import them into another instance of swimlane any applications or applets you export also contain their associated workspace, dashboard, workflow, reports, tasks, assets, and plugins if the application has integrations with other applications, they will be imported as well applications and applets are exported in a swimlane solution package ( ssp) file format if you plan to edit your ssp file after exporting it, see to ensure your ssp imports successfully after you work on it exporting and importing ssps can only be done by system administrators swimlane solution package exports include the initially selected, or root application or applet any additional applications associated with the root application workflow for the root application or applet or associated applications reports, workspaces, dashboards or export templates for the root application or associated applications integrations for the root application or applet or associated applications (including output mappings) assets and plugins associated with any associated integration mapped inputs to key store values (the keys are removed, but you can add them back after import) components of applications that are not included as part of the export are application history records or record history secure credentials and keys (key store) which can be added later after import secure values in asset configurations which can be configured again upon import exporting and importing swimlane solution packages can only be done by swimlane system administrators additional import/export ssp features select specific components when exporting content and import them into other swimlane instances any context or references to other applications are now maintained export multiple applications at once with the flexibility to choose what you want to export existing permissions in the destination now remain intact upon import provides a background job that cleans any orphaned objects that were created as an artifact from using other content migration tools export application ssps in turbine, there are a few ways to export an ssp first let's look at how to export from the applications & applets main page load the applications & applets main page, click the plus icon, and then select import or export a package on import or export a package window, step 1 has import and export radio button options click the export radio button turbine loads the available packages and components within those packages to export step 2 allows you to select the components you would like to export select the check mark next to components (i e , reports, applications, etc ) that you want to export, then click export if a component has an error, you may receive the error detected notification with an explanation this means that component cannot be exported successfully click close and review the component with the error to resolve if you select a component and the export is successful but contains potential issues, then you receive the a notification that provides information about the issue the export is still successful, and you can click close if you select a component and there are no issues, then your package exports successfully export from an application find the application or applet that you want to export and then, from the drop down menu on the application or applet, select export while you select one application or applet here, be aware that the export process packages all of the content associated with that initial application as a solution this means that your ssp may contain multiple applications and all that each application is associated with swimlane notifies you if there are potential issues that you need to be aware of related to your export in the example here, swimlane is letting you know that your current system has a task with an undefined (required) asset you should fix this now in the source system (since it is broken in the first place) you can continue the export and you will absolutely need to define this setting after import in order to have a complete solution in this example, the export has no issues, although a secure credential has been found secure credentials are not exported as part of solution packages when ready, click continue export the ssp is exported to your browser's default location for downloads