bcgov / bcgov/entity

Update Name Request field validation

Open
#7,692 2 comments 0 reactions 0 assignees View on GitHub
ENTITY - DO NOT USE Epic Name Request Names Team
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

## Background
Currently, there is very restrictive field validation for Name Request numbers. Staff often ask why the NR isn't working, when usually the cause is from restrictive field validation. They enter "1234567" instead of "NR 1234567", when NameX and NRO allow all kinds of variation in the field.

## Requirements document
https://docs.google.com/document/d/1g9HvsEt0eYBVKL4fss9n4UBSEBtCM-IiLZnw8Y2EeMQ/edit?usp=sharing
(wip, will be turned into a github doc)

## Acceptance Criteria
#### **Update the field validation to the following:**

**Allow:**
* Number only "1234567"
* NR with no space before number "NR1234567"
* NR in lowercase "nr1234567","nr 1234567"
* NR with single or multiple spaces before number "NR 1234567"," nr 1234567", "NR 1234567"
* Leading and Trailing spaces with or without NR " 1234567","1234567 ", " NR1234567","NR1234567 "

All of the above scenarios should be accepted for the search, but still normalized to the following format: “NR 1234567”

**DON’T allow:**
* if there is a space in the middle. 'NR 12 34567'

#### **Update the field validation in the following locations**
* Manage business dashboard, affiliation modal
* Edit UI (alteration and correction filing)
* Name Request application
* "I don't know my NR number" flow
* Existing NR search

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.