Steps for Publishing a Zapp

After you have successfully finished testing your Zapp, it is time to move it into Production. This article provides the key steps you should follow when publishing your Zapp.


1. Publish your Zapp in the Designer


In order to obtain access to the Update URL function and other configurations required to move your Zapp to Production, you must first Publish it in the Designer. You can do this by clicking the “Publish” button in the upper right hand corner of the Designer.




If any tasks in the Task Manager are still pending, a dialog asking if you wish to Publish with Issues or View Tasks will appear. Please refer to the Overview of the Task Manager article for more information.




If you still choose to publish your Zapp, a dialog will appear. Here, you may enter release notes for the version you are about to publish. Users will be able to see these notes in WorkSimple, in the Details dialog of the Zapp. Once ready, click “Publish.”




Note: Once you have published a Zapp version, you can no longer edit it. To make changes a new version must be created.



2. Update the Zapp URL


As a best practice, Capriza recommends building your Zapp in a test environment that, while similar, is separate from the production environment and contains test data. Once Zapp development and testing are complete, you need to point your Zapp to the production environment your end users will be accessing. To do so, you simply need to change the Zapp's URL within the Capriza Dashboard. Step-by-step instructions can be found in this article.


An additional round of testing is recommended using test accounts in the production environment to account for any discrepancies between the two environments.



3. Provide Your Customer Success Manager with Monitoring Information


The Capriza NOC team will proactively monitor your Production-version Zapp to ensure runtime and end-to-end service availability. Prior to Go Live, please provide your Customer Success Manager with the information detailed in this article so that the correct people may be contacted in case an outage or other service disruption is detected.



4. Define Distribution Groups


Published Zapps are distributed to users within your organization based on membership in a Group. Prior to pushing your Zapp to Production, you should define the group or groups to which it should be available. In general, we recommend specifying a smaller "Pilot" group of users for initial rollout as well as the overall group or groups. Please see Managing Groups and Managing Users for additional details.



5. Change the Environment


If your organization has multiple Capriza runtime environments configured (e.g. dev, test, prod), make sure the Zapp is pointed to the correct environment. Please refer to this article for detailed instructions. 



6. Release to Production


After publishing your Zapp, updating your distribution groups, and configuring the environment, you are now ready to release to Production. To do so, click the three dots icon to the right of the Zapp version to open the Zapp Options menu and select "Release to Production."




The following popup will surface.




Click the "+" icon to select Distribution Groups, and click "Apply" to confirm your selections.




Click "Release Zapp." A "Production" tag will now be visible on the Zapp version.




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


Please sign in to leave a comment.