Future Effective Filling - MBR State - VERIFY

[NaveenHebbale]

Future Effective Filling In MBR - Future Effective filling is shown as draft state as shown in a snapshot

[severinbeauvais]

@yuisotozaki FYI.

This applies to future effective IAs, registrations and amalgamations. When they are Filed and Pending, we consider them filings, not draft tasks.

1. What state should we say this item is in?
2. Should we have a tooltip? Should it include the FE date?
3. See also tooltip for FE address changes.

[yuisotozaki]

@NaveenHebbale What does this look like in COLIN?

Ideally, we show the user what it is. In this case, the state is Future Effective. Tooltip to show the FE date is a nice touch.

[severinbeauvais]

I think it makes sense to create a new pseudo-state, "Future Effective", in the MBR. It would apply exclusively to FE bootstrap businesses (incorporation applications, registrations and amalgamations).

[NaveenHebbale]

@yuisotozaki there is on MBR concept in COLIN. Please find the attached business snapshot

[yuisotozaki]

@NaveenHebbale Thanks for that screenshot.

I guess the question here is, does the user want to see the FE filing as a separate line in MBR? A couple of thoughts around this:

• User A might think, "I've already submitted that filing, so I don't want to see it in the list."
• User B might think, "I want to stay up to date with any FE timing. It's useful to me to see it as a separate thing on the MBR when I load the page."

User A might be an infrequent user whereas User B might be a frequent user (like a paralegal).

Applying agile to the design direction, I would keep it on the MBR as Future Effective. Hiding an FE from MBR sounds like it's going to add effort and we don't have a user feedback based reason to spend that effort.

[severinbeauvais]

Looks like COLIN says it's "Active", but I disagree with saying that in LEAR because we haven't created the business yet, and we don't have a business number for it yet.

Yui, I'm thinking User A might still want to see that they've done something. +1 for User B.

[severinbeauvais]

We worked on this in another ticket. Here are a couple of examples from Dev:

.

I'm changing this ticket to VERIFY.