A typical TrueContext deployment includes a Development FormSpace, a User Testing FormSpace (UAT) and a Production FormSpace.
Access and permissions for each FormSpace are managed through the creation of user Groups. Each FormSpace can have a different set of users with access. For example, you can have an HR Development FormSpace and an Inspection Development FormSpace, and assign a different set of “Development Users” to each FormSpace.
This is the path that your forms should take when copying forms and promoting them into a Production space.
-
Purpose: This FormSpace has a copy the developer can change at any time in the interest of improving the form. Only developers should be able to submit this form, if the developer breaks it while they are working it, they won’t affect anything that is in use in the field.
User Acceptance Testing (UAT) FormSpace (Optional but important)
-
Purpose: This copy gives you a version to use for testing by more than just the developers, while keeping the development copy for the developer to continue working on. A separate FormSpace for UAT provides a similar function to our Can Test permission but gives non-developers access. The developer can continue to work on the form without annoying users with frequent updates.
Note: You should copy Forms from Development or UAT. Don’t create or edit them in the Production FormSpace.
Before you copy from one FormSpace to another:
-
Ensure that you tweak the destinations that were copied to align with the FormSpace that they are in. For example, if you copy an Email destination over into Production, you might want the Subject, Body and To fields to be different than what you had in Development.
Once you have created the connections across your FormSpaces and copied over all your Data Destinations, it’s time to copy the form.
Note: The first time that you copy the form, select "Create Form" as the Target Form. Every other time after that, select the "Create as a New Version of an Existing Form" and copy it on top of the existing version so that you can maintain Version History even when copying forms between formspaces.
Use a naming convention so that as a developer or a tester, if you have access to more than one copy from the app, you know which is which. FormSpaces are not visible in the app — if someone has access to all three copies, they will show all the same name. Clear naming also helps when you are looking at submission data as it will be easy to see which version of the form you are looking at (Dev/UAT/Prod)
Here is an example of what your FormSpaces might look like with a consistent naming convention.
|
|
|
UAT - Job Hazard Analysis
|
|
DEV - Job Hazard Analysis
|
#TechTalkImplementation
------------------------------
Ian Chamberlain
Solutions Architect
TrueContext
------------------------------