Capriza supports version control to facilitate management of your Zapps. As a Zapp designer, you can create a new version for major updates or simply edit an existing version in place if the changes are small.
You can obtain an overview of all Zapps and versions via the Zapps page in the Capriza dashboard. The dashboard uses the concept of a Master Zapp, which includes a top level view of all the versions of a single Zapp as well as some common Zapp properties, such as the name of the Zapp, the description, icon, owner and the original creation date. Each Master Zapp that includes more than one version is represented as a “stack” of Zapps in the top level view.
A user can drill down and see a detailed list of all Zapp versions associated with that Master Zapp.
Each version of a Zapp has its own specific properties which include the version number, the dates it was created and last modified, adoption information, release notes, source app URL, distribution groups, the Zapp URL, and a few advanced settings.
The Zapp version numbers are whole integers and incremented whenever a new zapp version is created.
The Lifecycle of a Zapp can be divided into several key phases.
- Creation: The designer begins the process by selecting "New Zapp"in the Dashboard and creating a new Zapp using the Designer.
- Edits and Release: He or she can edit that Zapp as required and then release it to a small group of beta testers for testing and evaluation.
- Feedback and Iteration: The designer who created the Zapp receives feedback about that Zapp and creates a new version to incorporate changes. This can repeat several times until all stakeholders are satisfied.
- Production: Once the Zapp is accepted, the user releases the Zapp to production and makes it available to the relevant distribution groups.
- Further Iteration: After some time, the designer may wish to incorporate additional feedback from users and improve the Zapp. To do so, creates a new version and goes through the release process again.
- New Versions: Once the new version is approved, it’s released to production and replaces the existing version in production which is “retired” (tagged as "past production").
The following diagram describes the Zapp lifecycle:
A Master Zapp includes multiple Zapp versions but at any given time, there can only be one version of that Zapp defined as the Production version. A Production version is the Zapp version that is available to the distribution groups defined as the production groups. In addition, production versions are tracked more closely for errors and usage stats.
A user can choose to release a version to production which will tag that version as the production version of that Zapp.
Zapp Management is a broad topic that encompasses many nuances. To gain a full understanding of all features and processes, please refer to the following articles:
- Steps for Publishing a Zapp
- Editing & Updating a Zapp
- Zapp Cloning v. Versioning
- Archiving & Deleting a Zapp
- Combining Zapps
- Changing Zapp URLs
- Adding URL-Based Zapps
- Upgrading a Zapp