Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Overview:

Description

UI improvements for form builder add/edit process.

Type

Organic Feature

Story

Mockup

https://invis.io/HGKICLMBATR
https://invis.io/NHRYGE4BJM8
https://invis.io/PN10HL086DMW

Ticket

Assets

https://drive.google.com/open?id=0B0Ou1BX7e1gAWC1EMFJYY1htdWM

Quantitative Data:

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

  • Metric Value

HYPOTHESES

  • Lorum ipsum

REASONING

  • Lorum ipsum

Competitor Research:

Function

Findings

Image

Takeaways

EMBRACE

REJECT

TO DISCUSS

Proposal Feedback:

Stakeholder

Date

Changes

Product

11/03/21

DONE

  • 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 )

    • Toggle to turn on required message now as a prefix next to the input field

REJECTED

NEED MORE INFO

TO DISCUSS

Product

11/03/21

DONE

REJECTED

NEED MORE INFO

TO DISCUSS

TO DO

  • On field editor inputs have placeholders for all items that make sense (e.g. required message input could be ‘Required message’)

  • For ‘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

Retrospective:

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

  • Metric Value

HYPOTHESES

  • Lorum ipsum

REASONING

  • Lorum ipsum

  • No labels