Outstanding Work for the New Data Model

[kiiskila-bcgov]

Remaining Klamm Work

(IE 11 Compatibility)

---

High Priority

(Critical tasks that must be completed before go-live date.)

1. Form Builder Security & Policies
   • Ensure only form-developer roles can build forms.
   • Lock /build route when form is under-review or published.
   • Activity Log for form building.
2. Form Element Functionality
   • Fix Select/Radio options not saving on creation/edit.
   • Ensure new tags work in the edit modal (not just create).
   • Pass custom field attributes (min/max/options) to generated JSON.
   • Toggle default styling (borders/indent) on Containers.
   • Fix nesting non-containers (currently deletes elements in the UI/UX).
   • Show the UUID as read only in the element editor.
3. Form Builder UI/UX
   • Have common templates to pick from in the Scripts tab.
   • Update script/style name when build name changes.
   • Indicate in the script/style tab if an element is being used (change colour in list).

---

Low Priority

(Important but can be tackled after high-priority items.)

1. UI/UX Improvements
   • Show "deployments" section in form version view.
   • HTML Monaco editor for "Text Info" elements.
   • Help text in the form element editor explaining the different fields (ask Rob to write the help text).
   • Remove 'Visible' toggle from element
2. Naming & Clarity
   • Rename "Select Input" → "Dropdown Input".
   • Rename "Text Info" → "Text Display".
   • Drop "Input" from clean names of element types.
   • In element editor change "Name" -> "Element Name".
   • Make sure element fields that are required are actually required (value for text info).
   • Template list either filtering based on type or grouping based on type.
   • Searching the template list based on tags.
   • View/Manage all templates, but not edit, just turn on/off is_template and edit the tags.
   • Keep a connection of what field was cloned/templated from (table with source and target).
3. Technical Bits and Pieces
   • Lazy loading for nested children.
   • UI/UX should block nesting non-containers.
   • Caching implementation.
4. Import/Export
   • Import form version functionality.

---

Out of Scope

(Future ideas or non-critical tasks; revisit after go-live date.)

• Scripts/Stylesheets: Hide current item in import lists.

---

[kiiskila-bcgov]

Not sure the priority on these items, but here is a small to-do list of things we need to do, most are pretty small @brysonjbest @JohYoshidaBCGov

A non exhaustive list of some of the outstanding items we need to fix/implement:

• Make sure Select and Radio options are being saved on creation/edit in the form builder
• Fix the tests, they were temporarily disabled since they need to be updated to the new data model
• Make sure the policies are fixed so only form-developer roles can build a form
• Make sure the form builder /build route is not editable once a form version is under-review or published
• Make sure the "deployments" section of the form version page shows up in the view page of the form version
• Make sure adding a new tag works in the edit section of a form element. Right now it closes the edit modal and only works in the create form element modal.
• Make sure when you create a new form element from a template that it adds the custom properties like the select options' options

[JohYoshidaBCGov]

• Need to be able to add data bindings to form elements
• Dynamic visibility (via Scripts tab) instead of boolean on element
• HTML/Markdown editor for Text Info type elements
• 'Select Input' type is confusing - recommend changing to 'Dropdown Input'
• Recommend changing 'Text info' type to 'Text display' or similar
• Recommend dropping 'input' from the clean names of element types
• It's good that we can't change element type after creation, but sometimes form updates will ask us to change e.g. a dropdown to a radio, or a text input to a text area. I recommend merging dropdown/radio and text input/area elements and adding a toggle to select which one is used
• Ability to toggle default styling on Containers (the border and indent) would be nice & allow for better use of containers to organize form elements

[kiiskila-bcgov]

Moving this here for archival reasons

Builder

brysonjbest

• - Preview to our kiln
• - Generated JSON should be able to generate old template and new template
• - Script uuid autocomplete
• - Stylesheetuuid autocomplete
• - Make sure the the custom field attributes are passed to the JSON. So the min/max or options or other custom values that are unique to each field (not the generic form element values which should be being passed already)

kiiskila-bcgov

• - Form is_template (reuse element, but detached from original)
• - Form tags

JohYoshidaBCGov

• - Create new form version from existing version
• - Nesting non-container save, currently deletes the element from the UI/UX

---

• - Import form version
• - Lazy loading for multiple nested children when trying to generate json, or load the page
• - UI/UX shouldn't allow nesting of non containers
• - Caching of everything
• - Databindings, datasources, etc. Order for data sources in form version. And multiple data bindings per each field

Scripts

• - When you import script, it doesn't hot reload
• - The Script you are on should not be in the import list

Stylesheets

• - When you import a stylesheet, it doesn't hot reload
• - The stylesheet you are on should not be in the import list

[spencercrose]

Kiln has a componentMapping object that handles additional element types we haven't yet captured in the data model:

• Currency - It uses a custom CurrencyInput component formatted as CAD.
• Links (URLs) – Hyperlink (renders as a link).
• File – Probably can skip this one for now.

Other element "subtypes" we might consider since they are very common, or need special rendering:

• Email
• Phone
• Postal codes
• Hidden Field
• Barcode/QR Code Scanner, depending on how they show up in the XDP files.

[JohYoshidaBCGov]

Some required Kiln changes:

• Display Field Label instead of Element Name (Text input etc.)
• Display Container Legend/Title (preferably, set heading level based on container hierarchy)
• Recognize repeaters
• Correctly display HTML ordered lists
• Correctly display HTML ordered lists

[JohYoshidaBCGov]

It seems that floating fields [formStates['UUID'] only works with single quotes around the UUID, not double quotes, so the autocomplete in Styles and Scripts should use single quotes as well

[JohYoshidaBCGov]

Would be helpful if radio/dropdown options had a value that could be used in scripting instead of the label, so that we don't have to refer to a whole sentence (whose wording may change)