Problem Statement
An application could be designed in a way that requires "checks" to be made before even allowing for the application to be submitted.
For example, to be able to submit the application, the Applicant might need to be within a specific age range as defined somewhere else in the system (bad example, I know).
Currently, these kind of checks are made on the doBeforeSubmitting method of an ApplicationTypeService, and when the check "fails", an InvalidOperationException is thrown. The error is then displayed to the user.
The issue here is that the checks are evaluated one by one, and not all in one go. The user is only aware of a failing check, one by one, after they hit the submit button. The UX for this is pretty bad right now.
Suggested Changes
In a project that I was part of before, this was the card that was displayed on the Summary page of all applications, and showed that if each check passed or not.

If the user did try to submit the application when the checks were failing, they'll simply get an error message saying "Application Checks Did Not Pass, please check your application again.".
Code Suggestions
None as of right now - 29/05/2024
Problem Statement
An application could be designed in a way that requires "checks" to be made before even allowing for the application to be submitted.
For example, to be able to submit the application, the Applicant might need to be within a specific age range as defined somewhere else in the system (bad example, I know).
Currently, these kind of checks are made on the
doBeforeSubmittingmethod of anApplicationTypeService, and when the check "fails", anInvalidOperationExceptionis thrown. The error is then displayed to the user.The issue here is that the checks are evaluated one by one, and not all in one go. The user is only aware of a failing check, one by one, after they hit the submit button. The UX for this is pretty bad right now.
Suggested Changes
In a project that I was part of before, this was the card that was displayed on the Summary page of all applications, and showed that if each check passed or not.

If the user did try to submit the application when the checks were failing, they'll simply get an error message saying "Application Checks Did Not Pass, please check your application again.".
Code Suggestions
None as of right now - 29/05/2024