search

UK-SBCoA / uniform-data-set-dotnet-web

.NET Core implementation of UDS with MVC and Razor Class UI Library
BSD 2-Clause "Simplified" License
1 stars 0 forks source link

Milestone type property in VM #128

Open ashleybot opened 5 months ago

ashleybot commented 5 months ago

Currently the UI does not persist the milestone type on postback so the user would have to reselect type if they do not choose DECEASED or DROPPED on post.

See more here:

Something to point out is that because of the client-side validation for the milestoneType on the view, if a user selects NO FURTHER CONTACT for milestone type but then forgets to input an option for deceased or withdrawn

Screenshot 2024-01-31 at 11 51 54 AM

Then when the page reloads to show the validation errors, the milestone type WILL be changed after identifying that deceased or withdrawn are not selected, and setting it for continued contact. This is because when a form is loaded with either a deceased or withdrawn value, milestone type will need to be set to identity this as continued contact because they are neither deceased or withdrawn.

Originally posted by @mlan225 in https://github.com/UK-SBCoA/uniform-data-set-dotnet-web/issues/103#issuecomment-1919523133