severinbeauvais
commented
3 days ago In Figma, I asked @andyyanggov if sending additional messages (emails) would reuse the current continuation review controls. He responded:
Having not put too much thought into it yet, I'm thinking this might be a separate feature independent from the 'Review Result' controls. That way we keep the simplicity of the "no re-review" approach but allows a simple message to be sent without affecting the application status. It would share the same 'Previous Correspondence' section. We should definitely chat more about this.
Business team advised they often need to issue subsequent requests for a change in Continuation In application after the request has been issued, but client hasn't responded yet.
We already touched this topic during workflow design, and decided it could be challenging to handle it. Current design implies that staff issues a request and waits for the client to respond.
Melissa demonstrated to me a similar workflow for account management in the MBR product. When account is submitted, the BC Online team reviews the account submission, and communicates back to the client, if needed. The status is changed to On Hold while waiting for the client to respond, and subsequent communication is not supported until the response is received.
Possible risks/problems
• How state transitions and user responses will be handled if the requirement is implemented? It could make making the state management logic more complex and hard to maintain • More complex state management creates more edge cases and increases the risk of errors and the need for robust error handling • Users might be confused with the multiple notifications and overlook some of the requests • any other?