Reporting: Simple Report Final Report Review Page

[zoeyli-46]

Description

Before Industrial Reporters get to the "submit report" page, we need to show them a final review page that displays all the fields they have input into the system
This allows them to print and share the full report before submitting.

Acceptance Criteria

Given I am an Industrial Reporter who has completed my annual report
Before I am sent to the submit page, I want to see a full list of all fields for my annual report
So that I can review them before submission.

Given that I am submitting a Simple Report, and I am on the final review page, I see the following in read-only mode
Simple report final review wireframe

The user can click the following buttons: Back, Continue, Download

• The "Back button" will take the user to the Attachments page
• The "Continue button" will take the user to the Sign off page
• The "Download button" will download the page for the user

In the Final Review section of the task list, hide the “sign off and submit” section because the user is already in that section of the report.

Development Checklist:

• Create review-submit page similar to /bciers/apps/reporting/src/app/bceidbusiness/industry_user/reports/[version_id]/review-operator-data
• Create RJSF Schema with all steps and foldable groups
• Create UISchema
• (Maybe create accordion widget or edit css depending on review)
• Link redirect on previous compliance summary review page
• Perhaps create endpoint/service to grab all report data in one blob for RJSF if needed
• Add tests for backend endpoint
• Add tests for frontend page
• 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: