Skip to main content

What’s New

Qrvey 8.7
Version 8.7 of the Qrvey platform is now available to customers! This version includes new features including area charts, the ability to pivot and export data, as well as numerous bug fixes and performance improvements.
Learn More
Qrvey 8.6
Version 8.6 of the Qrvey platform is now available to customers. This version includes several new feature enhancements and performance improvements.
Learn More
Required Update for 8.5.1
Attention 8.5.1 customers: for any 8.5.1 instance deployed prior to 08/05/2024, an update is required to ensure you are running the latest images.
Learn More
Qrvey 8.5
Version 8.5 (LTS) of the Qrvey platform is now available to customers. This version includes several new features and performance improvements.
Learn More
End-of-life Schedule
We've added a new article that lists the features and endpoints that have been scheduled for deprecation. All features and endpoints will be supported for (1) year after the release date of the LTS version that contains the alternative.
Learn More
Version: 8.7

What is Content Deployment?

In Qrvey, Content Deployment refers to the process of copying content from one application to another, in the same environment or to a different one. Content Deployment is a powerful tool for managing all of the content generated (including Connections, Datasets, Web Forms, Charts, Pixel-Perfect Reports, and Flows) in a multi-tenant deployment.

Examples:

  • Copying an application that has been created in a staging environment to the production environment.
  • Copying some content, or an entire application created by one user to other users’ accounts.
  • Releasing the new additions to a baseline application to multiple tenants of the system.
  • Provisioning a copy of a baseline application to multiple tenants of the system.

How to Deploy Content

To open the Content Deployment page in Qrvey Admin Center, click the Content Deployment icon in the left-hand navigation pane:

Content Deployment Icon

To Deploy Content, follow these general steps:

  1. Create the source and target servers.
  2. Create a package and version of the source application.
  3. Create a Deployment Definition to specify the content to copy and what to change during the deployment.
  4. Create a Deployment Job to specify the recipient users and the destination instances, and they determine the value of all marked tokens for each recipient or group of recipients.
  5. Finally, run a Deployment Job to populate the target application with content.

Video Tutorials

For video instructions, please watch the Content Deployment Tutorial.

API-Based Content Deployment

For details, please read: