Mass manual reassessment part 2 (outcome view ui)
- Dominant language
- TypeScript
- Stars
- 29
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
## User Story
Enhance the Batch Manual Reassessment History functionality by allowing ministry users to view the outcomes of a completed batch in a separate UI screen.
When a batch manual reassessment has finished processing, the user will be able to select View from the history table. This will open a new UI page showing the results for that specific batch.
## Acceptance Criteria
### Batch Manual Reassessment History table update
- [ ] Add a View button/link in the action column.
- [ ] The View action should allow the user to access the results for the selected batch.
- [ ] The View action should be available once processing of the records for the batch is completed.
- [ ] Selecting View should navigate the user to the Batch Manual Reassessment Results page.
### Batch Manual Reassessment Results Page
- [ ] Create a new UI page that displays the outcomes for a selected batch manual reassessment.
- [ ] Have the ability to navigate back to the Mass manual reassessment screen
- [ ] Page content
> Ministry
> Mass Manual Reassessment Outcome
>
> Batch manual reassessment results:
> Batch ID
> Total Applications
> Successful (##)
> Failed (##)
>
Applications(##) (Blue header for top of table consistent with other tables) Search bar for application
> Success(##) Failed(##) <--- (these are tabs)
> Table
- [ ] Create two tabs for the table:
- Success
- Failed
- [ ] The number of applications in each category should be reflected in the corresponding tab where consistent with the application's existing UI patterns.
### Success Tab
The Success tab will display applications where the batch manual reassessment was successfully completed.
Sample Table
Application Number | Result | Action
Application Number | Success | View
Requirements
- [ ] Results should be paginated if the number of applications exceeds 10 as per the standard table behavior.
- [ ] If there are no successful applications display an message that aligns with our normal behavior (cat picture nothing here similar to the disability profile when its blank)
### Failed Tab
The Failed tab will display applications where the batch manual reassessment could not be completed.
> Table
> Application Number | Result | Failure Reason | Action
> Application Number | Failed | Application does not have a valid assessment calculation. | View
> Application Number |Failed | Application is date archived and not eligible. | View
Failure Reasons
- [ ] The Failure Reason displayed to the user should come from the outcome generated during batch processing.
- [ ] The expected failure reasons are:
- The application does not have a valid assessment calculation.
- The application is date archived and not eligible.
- The application is cancelled and not eligible.
- The application experienced an unexpected error.
### Table function
- [ ] Allow for the user to go back to the mass manual reassessment screen from the application screen
- [ ] View should navigate to the assessment view of the application page with the app history on the left (see screen shot for reference)

Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.