Staff needs to edit Firm Registration Completing Party when First Name is too long - Part 2 [ Future Work ]

[Rajandeep98]

• When the BCROS account is created, both First and Middle names are stored in the user's First Name.
• As such, the First Name field might become longer than 30 characters.
• When this happens, the Completing Party will fails validation on a Firm Registration filed by End User.

Current Workaround:

• End users provides the names breakdown.
• Staff user open the draft, enters the Completing Party with the name broken down as last, middle, first.
• Staff saves the draft.
• End User re-opens the draft and completes firm registration.

[Rajandeep98]

This Work is For Future, Needs Discussion to Create a new workflow for some filings where user is not allowed to edit some fields and staff helps them, as per permissions work the workaround would be blocked in certain filings as it checks on who is submitting the edited drafts, so we need a way to detect the un authorized changes which are being submitted by user were actually edited by staff so that it can bypass the restriction in place.

as of now to accomodate staff workaround we are skipping the name change detection in registration filings per reported by mihai.

[Rajandeep98]

some sample work:
bcgov/lear#4005

[Rajandeep98]

possible workflow:

[mstanton1]

@Rajandeep98 let's review this in refinement tomorrow @ 11.

[vikas-gov]

@Mihai-QuickSilverDev and @Rajandeep98 to test the scenario for API clients and confirm requirements

[Mihai-QuickSilverDev]

• The three of us met and had a closer look at the Completing Party functionality.
• We would have to reconsider API filings, in regard to what data this field should reflect.
• Will add here the As Is status from COLIN shortly.