Publish a Solution Version

Note: To publish a Solution version, you must have the "Publish Solutions" account level permission. To deploy a Solution, you must be Team Owner of a Project Team.

What does it mean to publish a Solution version and why do we do it?

By publishing a Solution version, that version can no longer be edited except for the Solution settings, Dashboard, Widgets, and Scheduled Tasks*. Solution versions are typically published for the deployment of the Solution as Solutions must first be published to be deployed. If a published Solution version is already deployed, users can publish a separate version of the Solution to overwrite any previous versions in all relevant Project Teams the Solution version is deployed to.

Note: If the Solution is deployed to multiple Project Teams and a Solution version is published, this will be applied to all Project Teams the Solution is deployed to.

* Changes to the Solution settings, Dashboard, Widgets, and Scheduled Tasks for the published Solution version must be made from the Solution. Changes to these cannot be made from the Project Team.

 

How to publish a Solution

You can also publish a Solution version by:

1. Navigate to the Solution you wish to publish
   
   
2. On the top left of the left panel of the Solution, using the "Currently viewing" dropdown, select the version you wish to publish
   
   
3. Click onto the "Publish this Version" tab
   
   
4. Confirm you are looking to publish the correct version
   
   Note: If the Solution is deployed to multiple Project Teams and a Solution version is published, this will be applied to all Project Teams the Solution is deployed to.

Alternatively:

Note: It is recommended that a Solution version is tested via a Test Team before it is published. Learn more about Test Teams

1. Navigate to the Solution in which you wish to publish
   
   
2. On the left panel, go to the "Versions & Publishing" tab
   
   
3. Click onto the 3 dotted icon under the "Actions" menu for the version you wish to publish
   
   
4. Click "Publish this version" to publish the version
   
   
5. Confirm that the version you want to publish is correct
   
   Note: Please ensure that the version you are publishing no longer requires editing at this stage as you will not be able to edit a published Solution version unless a new version is edit. Learn more about how to make edits to a published Solution version

Steps 6-7 will only apply to users if they have the "Create Project Teams" account level permission and are willing to also deploy a Solution version:

6. In the popup after publishing your Solution version, confirm that you wish to create a Project Team to deploy your Solution version
   
   
7. Enter the Project Team name and description and click "Create Project Team"
   
   Note: If a Project Team is created in this way, the Solution version you published will be the initial deployed Solution version in the Project Team.
   

What are some example scenarios that you should consider when publishing a new version?

To make this clearer, here are a few scenarios:

Scenario 1: Manager publishes Solution Version 1.0 and an end user starts an Assessment shortly after. Before the user finishes the Assessments, the manager publishes Version 2.0. When the end user returns to the Assessment, they will be continuing Version 1.0 of the App.

Scenario 2: Manager publishes Version 1.0 and then Version 2.0 before any end user begins running Assessments. When the end user begins an Assessment, they will be using Version 2.0 of the App.

Scenario 3: Manager publishes Version 1.0, then Version 2.0 and then re-publishes Version 1.0. When the end user begins and Assessment, they will be using Version 1.0.