Import Swimlane Solution Packages

you import swimlane solution packages ( ssp) into a swimlane system the packages contain at least one application or applet, along with all of the associated applications, tasks, assets, plugins, workflows, reports, dashboards, and workspaces that form a complete solution the import process handles some issues for you, either stepping you through the process or letting you know that there will be actions that will need to be taken once the import is finished the process also alerts you of critical errors that you need to be aware of while you cannot import the same content twice in a swimlane solution package since swimlane does not currently support content conflict resolution, promoting or migrating content from a dev environment (ssp export) into a prod environment (ssp import) will work as expected, as long as the newer instance is initialized with an ssp export/import from the older instance use case to safely test updates in a non production environment and later promote those changes back to production, follow these steps install the dev instance set up a separate swimlane dev environment for development and testing purposes export from prod and import into dev use an ssp export to extract all applications and necessary configuration from your existing prod instance import the ssp package into the newly set up dev instance to mirror the production environment make and test changes in dev perform your development tasks—modifying apps, creating new workflows, or testing updates—safely in the dev environment without impacting live operations promote changes to prod once changes are validated, perform an ssp export from the dev environment import this package into the prod environment to promote your updates best practice always ensure your dev environment is up to date with the latest content from prod before making changes this helps avoid conflicts and ensures a smooth promotion process you can upgrade plugins as part of the import process the process will notify you if there is a newer version of a plugin you are importing in order for your imported solution to be fully functional, you may need to address all of the issues swimlane points out during the import process exporting and importing swimlane solution packages can only be done by swimlane system administrators to import swimlane solution packages from the applications and applets main page taskbar, click the plus menu icon and then select import applications and applets you are prompted to drag and drop the file to the swimlane window, or you can browse locally for the file and select it for upload at this point, swimlane checks for errors and issues in the imported data three things can happen during this check swimlane detects an error and the import is rejected you are notified of the error swimlane detects issues, the import completes, and you are notified of the issues swimlane detects no issues and the import completes if there are issues with the import, swimlane notifies you with a review potential issues page issues that you can immediately fix are listed under a take action subheading issues that you can resolve after the import are listed under a take note subheading these subheadings only appear if there are two types of issues otherwise, you will simply be asked to review the potential issues in order to have a full solution post import, you should ensure that all of the issues are addressed! errors abort the import some examples of what can cause errors are duplicate content (applications and anything associated with them), name or acronym duplications, and plugins that require downgrades important! you cannot import the same content twice in a swimlane solution package swimlane does not currently support content conflict resolution, although it is planned for a future release