Spike : NR expiration handling in Continuation In workflow about entity HOT 6 CLOSED

@OlgaPotiagalova
@severinbeauvais Comment for Spike -
Allow replacement of expired Name Request #22086
Currently, when there is a draft IA/registration/amalgamation/restoration/continuation in filing and the NR has expired, our software (UI) blocks the draft from being resumed.

This epic is to change the software so that a draft with an expired NR can be resumed and the user can select a new (eg, re-submitted) NR.

At a minimum, the following need to be updated:

The My Business Registry table currently states that the application is no longer valid. The tooltip should be updated.
Filings UI (entity dashboard) currently blocks the draft from being resumed. This needs to be updated.
Create UI currently blocks the draft from being resumed. This needs to be updated.
Create UI will need to identity that the current NR is expired and allow for the selection of a new NR.

from entity.

Also, we have existing Legal API code that postpones a NR's expiry so it doesn't expire while awaiting completion of a future-effective application. We should update this (#22092) and we might also consider leveraging this code so that an application-under-review's NR doesn't expire. @NaveenHebbale , thoughts?

cc: @vysakh-menon-aot

from entity.

Analysis

before the Continuation In application started

Nothing can be done with an expired NR (where a non-expired NR can normally be "converted" into a draft application). I don't know what we would do different here.

after the Continuation In application draft is created and before application is submitted and paid

If a draft application exists and its NR expires, currently the draft cannot be resumed. This is the subject of epic #22086 .

after the Continuation In application is submitted and paid

As the application (and NR) are in BC Registry hands at this point, I think we should look into extending its expiry date if needed. (There is already Legal API code that does this to prevent NR expiry when an application is future-effective.) The catch here is that staff may request changes, and then the user could take a while to update the draft and resubmit it... and the NR could expire during that time. What should we do about this? That's a business question @NaveenHebbale @OlgaPotiagalova .

from entity.

The catch here is that staff may request changes, and then the user could take a while to update the draft and resubmit it... and the NR could expire during that time. What should we do about this?

We could, for example, make sure there's at least 14 days left before the NR expires, to give the user a buffer. And if the buffer expires then they're back at square 1. Should we then refund them? I don't know.

from entity.

to be reviewed by Olga/Naveen. Scheduled session with Biz today 07/03

from entity.

Business team votes are against the additional buffer option.

In long term run replacing the expired NR with a new one is the best option and it is technically feasible.

Epic has been created https://app.zenhub.com/workspaces/entities---olga-65af15f59e89f5043c2911f7/issues/gh/bcgov/entity/22086

The implementation can be done for Continuation In first, and then expanded to other filings where the NR expiration scenario is applied.

from entity.