Copy an Application

How to successfully set up a new test environment for an existing Knack application

Prior to copying the App, please check the "Update Big Button code of all Production Apps in Knack" #24411 epic to see if you need to update the big button code. If so, follow instructions for the Big Button code in GitBook and submit a pull request (PR). You can read on how to submit a PR in our GitBook.

If you are copying the "Mobility Services Portal" application, do not copy records. Instead, export existing records and remove PII. Afterwards, import records into the test application. You can read about it in this page

If you are updating Big Button code

1. Go to the Production app and follow all instructions for Copy an Application

2. After app is duplicated, go to the copied test app and update the JavaScript following the GitBook instructions for Big Buttons

   • Make sure to test that big buttons are working on the test version of the app!

3. Submit a pull request (PR) by following instructions in Github Version Control and link the PR to the related sub issues

4. After PR is approved, make sure to copy the code used in the PR to the Production version of the App

   • Make sure to test that big buttons are also working on the production version of the app! It should be the same as test.

5. Close sub issue and ✅ checkmark the list of apps below to signify it is done.

1

Notify Apps Team using Slack channel #atd-knack

Above is the message used in the slack channel when copying apps.

2

Log into Knack Builder using the Transportation Data Enterprise account

This will be the (Knack Builder – Primary Account) available on 1Password.

3

Search for the application you want to copy

4

From the ... icon dropdown, select "Duplicate App"

You will want to duplicate from a production application. It will follow this naming convention.

• APP ACRONYM | APPLICATION NAME | PRODUCTION

5

Change app name to TEST | APP ACRONYM | DD MMM YYYY | APPLICATION NAME

Knack will automatically append "Copy" to the end of the name. We want to change this name.

• Edit this out and use the format:

  • TEST | APP ACRONYM | DD MMM YYYY | APPLICATION NAME

Optionally you may pause tasks if you do not want them to run in test.

If you wish to speed up the copying process you may also uncheck duplicate records but this will make it significantly harder to test as there will be no records to work with.

The new duplicate app will show up on the list with a yellow dot next to the name signifying that it is in the process of getting copied.

6

Notify Service Desk Primary of email notification

Copying the app will take time. Knack will send an email to the Transportation Data Enterprise account when it is done.

You want to let the service desk primary know that you’re expecting the email confirmation from Knack so they will notify when the copying process is done.

7

After App is done copying, from the ... icon dropdown select "Manage Builders"

Add builders and the PM assigned to this application to the new duplicate app by selecting "Manage Builders"

8

Add new environment to the DTS Portal listing of Applications

This is used to keep track of all our knack applications. Select the PRODUCTION environment you have copied and Add Environment.

9

Add details about the new environment in DTS Portal

To find the Application ID, go to the Knack App > Settings > API and Code.

10

Optional: Delete old test environment from Knack and add Date Deleted record in DTS Portal

If applicable, delete the old test app and add the new one to DTS Portal.