SKIP AHEAD TO
Why would you make changes to your App?
Things to keep in mind when deploying
How does this affect my Project Team that has a published App already?
How to publish another version
What are some common scenarios that can occur when publishing new versions?
Why would you make changes to your App?
Over time, when a business process automated by Checkbox is changed or expanded, it is necessary for you to reflect these amendments in your App to ensure that it remains useful by being up to date.
It is also common in the initial stages after deployment to receive user feedback to make minor changes to the wording and design of Apps.
Things to keep in mind when deploying
When Checkbox Apps are published for deployment, they can no longer be edited.
Luckily, Checkbox utilises a simple version control to manage any changes to an App, especially if they have been published. You can duplicate a previous version of an App (e.g. version 1.0) and make the necessary changes in a new version of the same App (e.g. version 2.0).
How does this affect my Project Team that has a published App already?
A Project Team only reflects the version of an App that is published. There can only be one published version of an App at any time.
Publishing a new version of a deployed app will automatically update the Project Team so that any users kicking off a new assessment will be able to see the changes you made in your newly published version.
How to publish another version
- Go to “Versions & Publishing” in your App and click “+ NEW VERSION”
- Select the version you want to copy and name the new version you are creating.
Note: The version description is optional but can help differentiate between the versions.
- You will be redirected to the App Studio of the new version you created (In this case, “Version 2.0”). Make the necessary changes to this version
- Once the changes have been made, go back to “Versions & Publishing” in your App and click the dotted icon under the “Actions” column for your latest version (in this case, “Version 2.0”)
- Click “Publish” and confirm you want to publish your latest version (in this case “Version 2.0”
Note: Notice that Version 2.0 is now highlighted to signify that it is the currently published version. Also notice that the checkbox in the “Editable” column becomes unchecked after publishing. To edit your published version, repeat steps 1-5.
What are some common scenarios that can occur when publishing new versions?
Please see the below scenarios and the respective outcomes:
Scenario 1: A Team Administrator publishes version 1.0 and an end user starts an Assessment shortly after. Before the end user finishes the Assessment, the Team Administrator publishes Version 2.0.
Outcome 1: The end user will still be continuing Version 1.0 of the App.
Scenario 2: A Team Administrator publishes version 1.0 and later publishes version 2.0 before any users begin assessments.
Outcome 2: When the user begins an assessment, they will be using Version 2.0 of the App.
Scenario 3: A Team Administrator publishes Version 1.0, then Version 2.0 and then re-publishes Version 1.0.
Outcome 3: When the user begins or continues an assessment, they will be using Version 1.0.
CONGRATULATIONS! You now have the skills to build, deploy and make changes to your own Apps. For more advanced features and solutions, see our Knowledge Base.