24A. Change Request and Change Request Revamp

As a student I need to be able to change all aspects of my full time application in order to manage the increased complexity of the full time assessment.

Overview
This is flagged as an issue due to the complexity of the current change request processes and a need to create a more streamlined process due to the sheer number of items that need to possibly be changed in a full time application. The goal is to create a post COE edit process that allows us to utilize the base workflow as closely to now as possible.

Feature overview

Key outcome features

- Ability for the student to access a change function (edit post COE) from the application section that allows for a post COE edit that will follow all workflows. 1 ticket
- this change would trigger down stream behaviors except for exception and income validation. Parent, partner, and PIR processes would take place prior to it being ready for ministry approval 1 ticket to modify work flow and trigger the workflow
- Ability to flag when a change has occurred to any question in the app and flag it in some way when change request is submitted. 1 ticket to make it so when a question has been changed from the previous version the inputs that have been changed are highlighted in red similar to when information is missing
- Net new UI section for ministry review of these changes 1-2 tickets for new ui and acceptance process
- Treat as new reassessment and needs to trigger sequential reassessment. 1 ticket to ensure this behaviour and adjust as needed
- reuse the dynamic data (need to clarify with sig and dheepak) this was related to the workflow use)
- get entire app data and save in a new spot (need to clarify with sig and dheepak) this was related to the workflow use)
- creating new relations in the data base (need to clarify with sig and dheepak) this was related to the workflow use)

Sub features
- view edit history for clarity of previous changes and to understand change history (incorporate change requested edits into this feature as well) possible 2 tickets
- map related questions to higher level actions (eg. which questions effect PIR or each exception type)
- stop edit retrigger of unchanged workflow items (exception, partner declaration, parent declaration, and PIR)

Additional tasks
- rename current change request tab back to appeals to reuse current change request process for future true appeals work (step parent waiver)
- disable current change request processes

Workflows:

Workflow of data collection for submitted change request

The issue identifies no files, tests, or entry points. Start by splitting the post-COE workflow, UI, data, and reassessment requirements into scoped tickets and resolving the questions assigned to SIG and DHEEPAK; define completion criteria for each ticket.

Written by the indexing model from the issue text.