Skip to main content

What’s New

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
NodeJS Deprecation
AWS has announced that it is deprecating NodeJS 12, 14, and 16. To avoid any issues as a result of this deprecation, upgrade your instances of the Qrvey platform as described in this announcement.
Learn More
Version: 8.5

Customizing Qrvey Deployment

This document will help you customize a Qrvey Instance for different configurations like Composer URL, “From” email address, etc.

Overview

At a high level, a deployed Qrvey instance has 5 CloudFormation templates that create 5 pipelines (Widgets, DataRouter, Worker, Microservices and Admin). Each of these templates has a set of input parameters that are the configuration of that instance/deployment. An instance can be updated by updating these parameters which will in turn update all resources to use the new values.

All configuration changes typically require some setup outside of the Qrvey platform (email address verification or CNAME records for URLs) and then updating the Pipeline inside Qrvey. In this document, we’ll first show the steps on how to update the parameter for a single pipeline and then a section for all the steps to make a specific change.

Update a Single Pipeline

These steps will show you how to update the parameters for a single pipeline. In this example, we’ll be updating the QrveyCodePipeline but the same steps can be replicated for any of the other pipelines.

Step 1: Identify the CloudFormation Stack

  1. Log into your AWS Account and select the region where your Qrvey instance is located.
  2. Navigate to the CloudFormation console.
  3. Identify the cloudFormation stack for the Pipeline you want to update. You can search for “CodePipeline” and you should see the 5 stacks as shown in this screenshot.

customizing_deployment

Step 2: Update the CloudFormation template parameters

  1. From the CloudFormation screen, pick the CloudFormation stack matching the pipeline you want to update and click on the Update button.
  2. On the Prerequisites screen, pick “Use Current Template”. Click Next.

customizing_deployment

  1. On the parameters screen, find the option you would like to change and enter in the new value. Leave the rest of the parameters as they are. You can find the specific parameter for your use-case in later sections of this document. In this example we are updating the “From” email address by changing the parameter called “VerifiedEmail” (highlighted with yellow). Click Next after changing the value.

customizing_deployment

  1. Click on Next on the Configure Stack options screen.
  2. On the next screen (Review), review the changes you have made, select the Capabilities checkbox (if shown) and click on Update Stack to apply the changes.
  3. At this point, the CloudFormation stack will move to “UPDATE_IN_PROGRESS” state.
  4. Wait for the CloudFormation stack to finish updating. Once it’s done the status would change to “UPDATE_COMPLETE”.

customizing_deployment

Step 3: Trigger CodePipeline to deploy changes

  1. Once the CloudFormation stack has finished with the update, navigate to the AWS CodePipeline console.
  2. Identify the matching pipeline for the CloudFormation stack you updated in the last step. For the “QrveyCodePipeline” stack, the pipeline will be called “Qrvey_xxxxx_Worker”.
  3. Select the Pipeline and click on the Release Change button.

customizing_deployment

  1. This will change the Pipeline status to “In Progress” and once the Pipeline is done the status will change to “Succeeded”.

At this point, the changes are deployed and you can start using the Platform.

Update Deployment Settings

Follow these steps to update a particular setting in a Qrvey Platform’s deployment.

Change “From” Email Address

Qrvey platform uses AWS SES to send out all emails. These emails come from Automation or Page flows and also transactional emails like the “forgot password” feature.

To change the email address that is used under the “From” section you’ll need to add and verify the email address in AWS SES and then update the Qrvey deployment to use it. Here are the steps:

  1. Log into your AWS Account and navigate to the AWS SES console.
  2. Under the “Email Addresses” section click on Verify a New email address. Type in the new email address and click Verify. This will send an email to the specified address from AWS.
  3. Open your email client and click on the verification link under that email
  4. Go back to AWS SES to confirm that the “Verification status” for that email address has changed to “Verified”.
  5. Update the following CloudFormation Stacks and CodePipelines by following the steps mentioned here.
  • a. Qrvey Worker
  • i. CloudFormation Stack: “xxxxxQrveyCodePipeline”. Parameters:
  • 1. VerifiedEmail - enter the new email address
  • ii. CodePipeline: “Qrvey_xxxxx_Worker”
  • b. Microservices
  • i. CloudFormation Stack: “xxxxxMicroservicesCodePipeline”. Parameters:
  • 1. VerifiedEmail - enter the new email address
  • ii. CodePipeline: “Qrvey_xxxxx_Microservices”
  1. Once all Pipelines have finished updating you will start receiving emails using the specified “From” email address.

Change Composer URL

You can change the Composer URL to match your own domain. You would need access to DNS settings for that domain (Route 53 or similar) to be able to create a new CNAME record and SSL Certificate.

  1. Identify two URLs associated with your Qrvey instance:
    • The Composer URL — (e.g., https://qrveysample.yourdomain.com)
    • The API Domain URL — (e.g., https://api-qrveysample.yourdomain.com)
  2. Log into your AWS account and navigate to the AWS Certificate Manager console.
  3. Create a new certificate matching the URL/domain you would like to use. You can create a specific certificate for the exact URL or a wildcard (*.yourdomain.com). You can also import or use an existing certificate if you already have one. Here’s a document about creating certificates. We recommend using DNS validation.
  4. Once the certificate is verified (status changes to “Issued”), copy the ARN.

Note: If your Qrvey Installation is in a region other than us-east-1 then you will need to repeat steps 2-4 for us-east-1.

Note: Starting on v8.4 the Widget URL is the same as the Composer URL.

Update MainTemplate

  1. Navigate to AWS Cloudformation console.
  2. Find the stack called Qrvey-----MainTemplate.
  3. Navigate into Update > Use Existing Template > Update and replace any parameters using the old URLs (composer or API) to use the new ones.
  4. Apply the changes and wait for the update to finish.

Update CloudFormation

Update the following CloudFormation Stacks and CodePipelines by following the steps from Update a Single Pipeline.

  • a. Data Router
  • i. CloudFormation Stack: “xxxxxDataRouterCodePipeline”. Parameters:
  • 1. QrveyURL - enter the new Composer URL.
    2. certificateARN - enter the SSL Certificate ARN
  • ii. CodePipeline: “Qrvey_xxxxx_DataRouter”
  • b. Widgets
  • CloudFormation Stack: “xxxxxWidgetsCodePipeline”. Parameters:
  • 1. ComposerURL - enter the new Composer URL
  • ii. CodePipeline: “Qrvey_xxxxx_Widgets”
  • c. Qrvey Worker
  • i. CloudFormation Stack: “xxxxxQrveyCodePipeline”. Parameters:
  • 1. sslCertificateNameDesired - enter the new Composer URL
  • ii. CodePipeline: “Qrvey_xxxxx_Worker”
  • d. Microservices
  • i. CloudFormation Stack: “xxxxxMicroservicesCodePipeline”. Parameters:
  • 1. sslCertificateNameDesired - enter the new Composer URL.
    2. CertificateARN - enter the SSL Certification ARN
    3. AdminAppDomainURL - “https://<composerurl>/admin/api”
    4. AdminServerURL - “https://<composerurl>/admin/api”
  • ii. CodePipeline: “Qrvey_xxxxx_Microservices”
  • e. Admin Center
  • i. CloudFormation Stack: “xxxxxAdminAppCodePipeline”. Parameters:
  • 1. QrveyURL - enter the new Composer URL
  • ii. CodePipeline: “Qrvey_xxxxx_Admin”
  1. The next step is to find the value for the CNAME record to be added to your DNS.

    • a) Navigate to AWS Cloudformation console
    • b) Find the stack called “Qrvey-----WidgetsCodePipeline”. Select Outputs Tab. Copy the value for “CloudfrontDomainName”. This will be the destination for composer URL CNAME record.
    • c) Navigate to AWS API Gateway console. Click on Custom Domain names
    • d) Select the domain matching the API Domain URL. Copy the value for “API Gateway domain name”. This will be the value for API Domain URL CNAME record.
  2. Login or navigate to your DNS provider (Route 53 or similar) and add or update the CNAME records for Composer URL and API URL with the values from last step.

  3. Run the Lambda Function:

    • Navigate to AWS Lambda console. Find the function called -----_CreateEnvFile_LambdaFunction. Click the function name to open the details.
    • Select the Test tab:
      • Enter any string in event name.
      • Add this JSON to the body:
        { "RequestType": "UpdateEnvFile" } 
      • Click Test.
    • Again, selecting the Test tab:
      • Enter any string in event name.
      • Add this JSON to the body:
        { "RequestType": "UpdateVariables" }
      • Click Test.
    • Wait for the function to finish and then you can start using the new URL.
  4. Once all the pipelines have finished successfully you should be able to launch Composer using the new URL.

Note: If you or your users have created content inside Qrvey Composer (Pages, Workflows or Webforms) using the old URL then those may not work properly. Any new content will use the new URL but any old content may still have the URL saved somewhere. Please contact Qrvey support for guidance on how to update the URL in content.