Admin\My Operator - External user can view and update existing operator information

zoeyli-46 commented 3 months ago

Description:

As an External User, given that I have registered in BCIERS, I can view and update my existing operator information, and fill in any new operator information fields asked in registration part 2 Figma link

Acceptance Criteria:

Given I am an authenticated user with the industry-user or industry-user-admin role, When I click on the My operator tile, Then I am brought to my operator page Operator page

Given that I am on my operator page, When I click edit Then it turns into editing mode Figma link

Given that I am on the Operator Information form, When I select General Partnership or Limited Liability Partnership Then the fields for a Partner appear

Given that I am on the Operator Information form, When I select “yes” to “Does the operator have one or more parent companies?” Then the fields for a parent company appear

Given that I am on the Operator Information form, When I select “yes” to “Is the parent company registered in Canada?” Then I see the field “Parent Company CRA Business Number:”

Given that I am on the Operator Information form, When I select “no” to “Is the parent company registered in Canada?” Then I see the field “Parent Company Tax ID Number:”

Edit-mode of operator information https://www.figma.com/design/LsDmLDCdnJqI8UahyqvOD8/BCIERS-Designs?node-id=8638-2726&t=oDdZLbbRzQ0FvNal-4

Development Checklist:

Updates to Parent Operator data model:

[ ] make cra_business_number field nullable
[ ] add field tax_id_number (nullable, varchar)

Create new data model Partner Company with fields:

[ ] partner_legal_name (varchar, required)
[ ] partner_trade_name (varchar, nullable)
[ ] partner_business_structure (FK to Business Structures table, required)
[ ] partner_cra_business_number (required)
[ ] partner_bc_corporate_registry_number (required)

Some other changes to data models will be required later, but because they impact existing prod data, I suggest leaving them as-is for now until we confirm with the biz area when they'd like the changes to take effect in prod.

Posibly updates dashboard tiles:

[ ] In bc_obps/common/fixtures/dashboard/administration/external.json\My Operator ensure tile href is correct
[ ] In bc_obps/common/fixtures/dashboard/bciers/external.json\My Operator ensure tile href is correct

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

Dependencies

zoeyli-46 commented 2 months ago

@nanyangpro this ticket's AC is ready for your review

zoeyli-46 commented 2 weeks ago

@BCerki edited this ticket to include the conditional fields, does it make sense or does it require more details?

BCerki commented 2 weeks ago

@BCerki edited this ticket to include the conditional fields, does it make sense or does it require more details?

Yup, looks great, thank you!

bcgov / cas-registration