Zapp Cloning v. Versioning

The Capriza Dashboard provides the option to create a new Zapp version or clone a Zapp. This article describes the differences between these two options and when each option is most appropriate.


Zapp Cloning v. Versioning


The key similarities and differences between cloning a Zapp and creating a new version of a Zapp are as follows.



New Zapp Version

Cloning a Zapp

Version Numbering

New version number will be one larger than the previous version.

A cloned Zapp is treated as an entirely new Zapp and will begin at version 1.

Zapp Owner

Remains the same.

The same Zapp Owner is carried over but can be changed in the Master Zapp Details dialog.

Zapp Distribution List

Not carried over between versions.

Not carried over when cloning a Zapp.

Master Zapp Details

Master Zapp Details, such as title, description, owner, and icon, are maintained for all versions of the Zapp.

Master Zapp Details, such as title, description, owner, and icon, are copied to the cloned Zapp.

Release Notes

Release notes are unique per Zapp version and will not be carried over when a new version is created.

Release notes are carried over to the cloned Zapp.

Production Version

To place a new Zapp version into Production, the previous Production version will be taken out of Production. A tag indicating "Past Production" will appear on that Zapp version.

As the original and cloned Zapps are treated as two separate Zapps, both can have versions in Production simultaneously.

 Two Zapp Versions

Cloned Zapp


When to Use Cloning v. Versioning


Zapp cloning is most appropriate to use when migrating between different environments (e.g. from development to QA). In this manner, you can keep the various iterations within each environment separate and, if necessary, assign a different Zapp Owner. In addition, in cases where you make a major overhaul to your Zapp (e.g. a complete redesign or styling update), you may wish to begin the Zapp version count again at one. Moreover, cloning can simplify the Zapp building process when creating multiple Zapps that begin with a similar workflow as you can simply change the end of the flow rather than starting from scratch.

Zapp versioning, on the other hand, is appropriate when making more minor updates to existing Zapps and in cases where you wish to maintain the same Zapp Owner and an ongoing count of Zapp versions.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.