Create a design mock-up for missing required information on sign and submit

[natalia-fitzgerald]

Create a design mock-up for missing required information on sign and submit.

Include:

• Mock-up of view on page load
• Mock-up of view on submission

Bucket 1: Missing information required to file (that is not required prior to this step)

• We will provide specific next steps for the user
  • Lapsed LEI
  • Visit GLEIF for instructions on how to reactivate your LEI
  • Email our support staff
  • Missing TIN
    • Visit update your financial institution profile for instructions
    • If your financial institution does not have an RSSD ID, provide your TIN below

Bucket 2: Missing information information required to file (that is required prior to this step)

• Missing anything else that shouldn't be missing by the time the user reaches this page, for example headquarter's address, Type of financial institution, or voluntary reporter status
• We will not load incomplete data
• We will load an error alert and a link to email our support staff

[dan-padgett]

@natalia-fitzgerald For the second bucket, "missing anything that shouldn't be missing" sounds like a catch-all that's meant to say "missing anything that isn't a part of bucket 1, and we're not sure why it's missing". Should we add type of financial institution and voluntary report to the bucket 1 list, since those are things the user could correct? I know we have logic built into the flow to makes those required, but if bucket 2 is a catch all for inexplicable missing data, we may want to scope it a bit more.

[natalia-fitzgerald]

@dan-padgett If they reach sign and submit and they haven't provided "Type of financial institution" or "Voluntary reporter" then it's a sign that something has gone wrong with the system, because these are required before a user can reach this step.

I updated the buckets but the general idea is that for anything other than the two requirements that haven't blocked a user from progressing prior to this step, we will not show incomplete data and instead show a general error alert and a link to email our support staff.

I am showing this on the View your financial institution profile page and the Sign and submit page because both instances indicate a similar issue.

A problem occurred when trying to load...

View	Sign and submit

• @angelcardoz

[dan-padgett]

@natalia-fitzgerald The updated bucket descriptions make a lot more sense, thanks! GH isn't letting me view the images in greater detail, but I think I can read the text enough to see that it looks good (and I think I found the relevant Figma page too).

[natalia-fitzgerald]

After yesterday's Desv/Design Sync we have the following next steps:

• Include LOU language into the sign and submit language around lapsed LEIs
• The backend will be set up to accept all registration statuses (for example, issued, lapsed, retired, merged, etc.)
• Rework content for the error alert to specify that LEI registration status must be issued in order to file…and make the action step more general --- contact LOU, go to GLEIF to figure out your LOU OR email our support staff

[dan-padgett]

Capturing some information relevant to the LEI alert:

• "Active" is a term to describe an entity's status: the entity is active, the LEI is not
• For the purposes of filing, it's the LEI registration status that matters, and the registration status must be "Issued"
  • The LEI registration status could be several different values, but the ones that we are concerned with are "Lapsed" and "Issued"
• For design, there is a question about whether users only need to see that they need to renew their LEI registration to know what to do, or whether they also need to see the specific registration status so they also know what our system requires.

[natalia-fitzgerald]

We have landed on two possible approaches to the LEI alert. There is still some discussion happening about what LEI statuses our system will potentially show.

In discussions with various team members I have heard that potential statuses are:

• Limited to Lapsed, Issued, and Pending Validation
• Limited to Lapsed, Issued, Retired
• Not limited and may include any GLEIF registration status

Can we determine which of the above will be true for our system?

Here are the options for the label:

• LEI status
• Registration status
• LEI registration status

Option 1. You must renew your LEI registration	Option 2. Your LEI registration status must be "Issued"

• @angelcardoz @dan-padgett @hkeeler @nongarak

[billhimmelsbach]

I think option 2 is the most accurate and flexible with potentially rare statuses. 👍

[natalia-fitzgerald]

Ok, it sounds like we are landing on Option 2, in order to maximize flexibility. @angelcardoz - Can I get your review on this and we will move forward with implementing?

Option 2. Your LEI registration status must be "Issued"

[angelcardoz]

@natalia-fitzgerald, I'm good with option 2. I think the use of "status" might be confusing to some people, but we can wait to hear from users.

[natalia-fitzgerald]

Here are all of the mock-ups covered under this ticket.

• @billhimmelsbach @dan-padgett @angelcardoz

Lapsed LEI or missing TIN on page load	Server fails on page load	Server fails on submission	Lapsed LEI or missing TIN on submission

[natalia-fitzgerald]

@angelcardoz @nongarak In our DSR/Frontend meeting @hkeeler mentioned that our system will only show Issued, Lapsed, and Retired. The alert messaging we have decided to implement is flexible to account for "Lapsed" and "Retired." BUT, it is not particularly helpful for those with a "Retired" status.

Outside of the scope of this task, the team may want to determine what the next step would be for a user that finds themselves in a "Retired" status and whether the next step depends on whether the LEI registration is retired in the middle of a filing period, in the middle of an activity year, or in a past filing that is being reopened.

[dan-padgett]

Only comment on the latest mockups is to add a comma in the second sentence for lapsed LEI registration: "If you need to renew you LEI registration, contact ..."

[natalia-fitzgerald]

Only comment on the latest mockups is to add a comma in the second sentence for lapsed LEI registration: "If you need to renew you LEI registration, contact ..."

@dan-padgett - Ok, updated here: https://github.com/cfpb/sbl-ux/issues/25#issuecomment-2462888667

[natalia-fitzgerald]

@billhimmelsbach These mock-ups are ready for development. They are also in Figma.