Follow

Steps for Moving a Zapp to Production

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 proceed with moving your Zapp to Production, you will first need to Publish via the Designer. Follow the steps in this article to complete the process.

 

 

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. Distribute Your Zapp

 

Use the distribution dialog to distribute your Zapp. See this article for details.

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

0 Comments

Please sign in to leave a comment.