Custom Form Components — Discuss, Assess, Prioritize

[acoard-aot]

Describe the task

There are a number of custom form components we have discussed that would help the LRS team. This task is about enumerating those components, identifying the important ones, and then making those ones concrete. Previously our discussion of these custom form components has been pretty high level, so we would need to make them concrete by finalizing UX behaviour, establishing where data is coming for features, etc.

Components

• Address GeoCoder - BCGov Geocoder has already been explored partially for static site, but we would have to look at integrating it with forms.
• Profile Details Auto-Filler - The ability for a user to copy over their profile info (name, address, etc) to a form. They may wish to copy this to the Applicant section, or they may wish to copy it to another section, so we may want a button that gives user control over this functionality? Needs discussion.
• Land Legal Description Component - Part of SDS form. Kerri says would help a lot if we could auto-fill this section based on PID data. This includes the "Legal Description" field which people often get wrong. The data for this may be stored in SITE, but unclear if in application or db.
• Map — See Custom Map Component #310.

Acceptance Criteria

• We've done an inventory of previously discussed components and have added all of them to this ticket.
• PO and team have reviewed which components we want to add, and if we want to include them then tasks have been created for that.

Additional context

• Add any other context about the task here.
• Or here