Global Forms
- Danny Hannah
- Barnaby Murtagh (Unlicensed)
Target release | Q1 2021 |
|---|---|
Epic |
|
Document status | DRAFT |
Document owner | @Danny Hannah |
Designer | @Amish Ladhu |
Tech lead | @Rokas B @Thejani Warunika |
Technical writers | @Danny Hannah |
QA | @Anu Kalangi |
Objective
Globalising of forms is a core objective for the product team. Our goal is to have a central management area for all forms in your Convertr platform and be able to reuse forms on multiple campaigns and make changes which update all of them at once, thus reducing repetitive work loads for our clients, reduce duplication both from a technical and management perspective.
Background
Forms are a requirement for all data entry into Convertr - everything has to be linked to a form, and in most instances mapped to the fields of the form (there are some exceptions here Facebook, LinkedIn and Eloqua to name some examples).
Currently, forms are linked to campaigns, are unique and have no ties to other forms. If you want the same form on another campaign then you have the ability to duplicate it but this means that the forms are still independent and a change on one will not reflect on the original. This works well in some instances but some clients have hundreds or thousands of forms which are largely the same which would be much easier managed from a central location.
Success metrics
Goal | Metric |
|---|---|
| |
|
|
Assumptions
Form level functionality should remain them same but at a global state (form types, translations etc)
Forms should continue to be available for Super Admin, Admin, Agency and Creative Manager users
Requirements
Requirement | User Story | Importance | Jira Issue | Notes | |
|---|---|---|---|---|---|
| 1 | Must be able to create reusable forms | Admins, Agencies and Creative Managers should be able to create forms which can then be easily linked to multiple campaigns. Changes made on the form should be reflected across all the linked campaigns. | HIGH |
| |
| 2 | Forms must still maintain a campaign relation | As a lead, I need to be linked to a campaign and a specific form. This means that we need a way to attribute the form to the campaign and thus the lead. We have agreed that on the global level you will define a url slug which will be consistent across all forms, but each campaign association will prepend the slug with the campaign id. E.g. form slug will be | HIGH |
| |
| 3 | Must maintain functionality to import forms from CSV on a global level | As a user, I should be able to generate a form from a CSV file. This is when I may have many fields which can be time consuming to create from the interface. I should be able to download a template to help me upload the right fields, and I should be able to set the following information for each field in my form:
|
|
| |
| 4 | Must maintain functionality to duplicate forms on a global level | As a user I should be able to choose an existing form and duplicate it, deciding whether or not to copy the campaign associations or not. I should also be required to set a unique name and form slug for my new form. |
|
| |
| 5 | Must be able to archive forms | As a user, I should be able to archive forms to keep my interface clear and to prevent forms from accepting data. This is a new feature which would replace the enable / disable functionality which is currently loosely implemented. I should still be able to access and re-instate my forms but if trying to view an archived form I should receive a warning that my form is no longer in use. |
|
| |
| 6 | “Roll up” campaign forms and merge them into a global form where possible |
|
|
| |
| 7 |
|
|
|
|
|
User interaction and design
Open Questions
Question | Answer | Date Answered |
|---|---|---|
|