Exporting a Register Template from sandbox to a live site in Assurance
Who is this article for?Administrators who want guidance on transferring a Register Template between Assurance sites.
Administration access is required.
Assurance allows you to export a Registers and Forms Template from one Assurance site and then import it into another site.
This means that a template you have been working on in the sandbox site can be imported into your live site directly instead of building the template from scratch.
This article shows you how to complete the export process.
1. Exporting considerations
Before performing the export, it's important that you consider what is and isn't moved as part of this process.
| Exported | Not exported |
| Default view | Conditional notifications |
| Description | Forms created in the Register |
| Eligibility criteria | MergeDocs |
| Fields (including dependencies, visibility, formula fields, sections, tables) | Public link settings |
| Instructions | Recommended actions |
| Name | Recommended checklists |
| Notification before and after End Date |
Reference documents |
| Prefix | Workflow approvers |
| Stage name | |
| Super sensitive |
2. Exporting a template
To export a template:
- Open the sandbox Assurance site to export from.
- Go to Registers & Forms Templates.
- Select the template.
- Click Export Template.
Your browser will export the template as a JSON file which you can save to your PC. You do not need to edit this file at all. - Open the other Assurance site to import to.
- Go to Registers & Forms Template.
- Click +Create Registers & Forms Template.
- Select Import Template.
- Upload the JSON file downloaded earlier.
An Import Registers & Forms Template progress screen will appear. You can either wait for the import to finish or the Notification Bell will alert you when the import is complete.
This feature will export the Details of the Register Template, the Workflow Stages (excluding Approvers), and everything set up under the Fields tab including formula fields, dependencies and default view.
3. Setting up a template
Further set up of the template is done on several tabs.
Below is some key information that is needed:
- Details - Basic template information
- Workflow - Management of the stages and approvals
- Fields - Management of the fields
- Notifications - Management of the notifications
- MergeDocs
- Reference Documents
- Recommended Tasks
- Recommended Checklists
- Public Link - Management of the template availability to external users
- History - Provides information around template changes
4. Troubleshooting common issues
There may be some errors when you try to import the template.
The most common errors are:
- "Name has been taken"
This happens if there is already a template with the same name. To fix this, change the name of the template and re-export it. - "Prefix has been taken" This happens if there is already a template with the same prefix. To fix this, change the prefix on the template and re-export it.
-
"Field exists with different parameters"
This occurs if you have a field in the new template that has the same name as an existing field, but it be a different field type or has different answers. To fix this, ensure conflicting fields are given a unique name or the field parameters in the import template match the destination site. - "Presentation is invalid"
This error usually relates to the visibility of default fields like Title and Person Responsible. To fix this, set the visibility of default fields to Mandatory and re-export the template.