Overview:
Description | UI improvements for form builder add/edit process. |
---|
Type | Organic Feature |
---|
Story | invis.io/HGKICLMBATRinvisio/NHRYGE4BJM8https://invis.io/PN10HL086DMW Ticket | ...
Quantitative Data:
Info |
---|
Data driven justification for ux/ui changes, especially necessary for organic changes that do not originate from client requests or roadmap features. |
Link | Date Range | Item | Metric & Value | Assumption |
---|
| 00/00/2021 to 00/00/2021 (0 Days) | | Metric name | |
...
Competitor Research:
Function | Findings | Image | Takeaways |
---|
| | | Status |
---|
colour | Blue |
---|
title | TO DISCUSS |
---|
|
|
...
Proposal Feedback:
Stakeholder | Date | Changes |
---|
Product | 11/03/21 | Rearrange UI so field controls are in top right of field editor (follows more traditional UI expectations rather than being in various places)
‘Type’, ‘Name’, ‘Enabled’ toggle are the 3 settings required for a field to be active within a form and are therefore most prominent at the top of each field editor Controls for field in top right of field editor now use consistent UI with rest of platform buttons and controls ‘Required’ toggle and message, ‘Label’, ‘Placeholder’ and 'CSS' class moved onto second row of each field editor, where these settings are deemed as the optional settings for each field
Consolidate field settings into single dialog (reduces layout shift as fields no longer appear depending on different types, reduces scolling as field height is smaller)
‘Edit Options', anything under ‘Advanced Options' dropdown (e.g. ‘constraints’, 'default value’) a single dialog tab called 'Options’
‘Choices' moved into same single dialog as above under ‘Choices’ tab
Improve the current disjoint between ‘required’ toggle and ‘required message' (before the required message would appear if a checkbox was turned on creating layout shift )
Status |
---|
colour | Yellow |
---|
title | need more info |
---|
|
Status |
---|
colour | Blue |
---|
title | TO DISCUSS |
---|
|
|
Improve processr configuration layout and therefore improve layout of form field options
Disabled field inputs and settings (https://docs.google.com/spreadsheets/d/1v1_36NJqSetStXY3J1_XQRi1WvZ528isOSHYRm4IB44/edit?usp=sharing - https://convertr.atlassian.net/browse/DAS-1235) |
Product | 11/03/21 | Status |
---|
colour | Yellow |
---|
title | need more info |
---|
|
Status |
---|
colour | Blue |
---|
title | TO DISCUSS |
---|
|
|
Product | 15/04/21 | |
TO DOFor ‘settings’ tab for each fields, have 3 tabs
Configure (HTML type would need default value slapped into this)
Remove ‘constraints’ (will still be available through processr job) and therefore will need to move ‘default value’ into ‘Configure’ tab Status |
---|
colour | Yellow |
---|
title | need more info |
---|
|
Status |
---|
colour | Blue |
---|
title | TO DISCUSS |
---|
|
|
...
Retrospective:
Info |
---|
To be completed after this features release. The retrospective should allow a basis for further improvements to this feature. |
User Feedback
Stakeholder | Date | Description |
---|
| | |
| | |
Quantitative Data
Link | Date Range | Item | Metric & Value | Assumption |
---|
| 00/00/2021 to 00/00/2021 (0 Days) | | Metric name | |