Dashboard\Tiles - External user condition if Operator record has 1 operation in status "Registered"

[zoeyli-46]

Dev Note: this is the second implementation of conditional dashboards based on if Operator record has 1 operation in status "Registered".

Dependencies

• 2047, #1960 External user can select operator/add new operator

Figma links

Please review this workflow Figma to see where each screen leads to by following the arrows/text instructions

Click through this Prototype to see the intended workflow for an external user who is signing into BCIERS for the first time and adding a new operator

Note: the grayed-out tiles in the prototype will be a future enhancement; for the MVP, we will implement them as hidden instead of grayed-out, because we already have the "hide tile" pattern implemented.

Description:

During the first year of BCIERS 2025, the Operator must complete a sequence of steps. To enforce this sequence of steps, tiles will be hidden and shown to users one by one given that they completed the required step.

Given that an operator is being created in BCIERS for the first time, these are the required steps

1. User signs in
2. User adds a new Operator by filling out Operator Information form (no approval needed from Internal User)
3. User becomes admin (no approval needed from Internal User)
4. User redirected to the BCIERS dashboard: only Admin and Registration and Report a Problem tiles are shown, (reporting and COAM are hidden)
5. If operator does not have 1 registered operation, registration tile's Register an Operation link has an "action required" notification
6. Given that the user registers 1 operation, when they return to the BCIERS dashboard the reporting tile is unhidden and shown 7. Given that the user has submitted a report, the COAM tile is unhidden and shown (pending BA decision on when to show the COAM tile)

Acceptance Criteria:

When I have logged in with access to an "Operator" without any operations registered The Administration, Registration tiles are both unhidden I see an "action pending" in my Registration tile next to Register an Operation Figma

Given that I registered one of my operations, then when I go back to my dashboard, the Reporting tile becomes unhidden Figma

Development Checklist:

• [ ] If helpful, see conditional dashboard tile logic and condition for required fields in PR

• [ ] Create API to return result if Operator record has 1 operation in status "Registered"

  • [ ] If Operator record has 1 operation in status "Registered"
    • [ ] Display dashboard tile\link: Registration\Register an Operation
    • [ ] Display dashboard tile: Reporting
  • [ ] If Operator record does not have 1 operation in status "Registered"
    • [ ] Display dashboard tile\link: Registration\Register an Operation - action pending
    • [ ] Do not display dashboard tile: Reporting

• [ ] Add routing protections for Reporting dashboard based on if Operator record has 1 operation in status "Registered"

• [ ] Meets the DOD

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:

[zoeyli-46]

Hey @patriciarussellCAS this is the ticket for graying out the tiles in relation to selecting an operator/registration part 2 flow. feel free to check the prototype in the first link to see how it is intended to behave!

[zoeyli-46]

Zoey to update this ticket / split it into 2 tickets, one for the operators who are registering for the first time and one for returning operators. remove the "graying out" part, replace with "hide" since that is already a pattern that has been implemented.

[zoeyli-46]

@shon-button ticket has been split into this and ticket #2341 let me know if there are clarifications I can make to this ticket!