ore-ero
ore-ero copied to clipboard
canada-ca
Multiple uses in software
An administration can have multiple uses for a single software. Is this something we want to encourage. It would be simpler to only allow a unique use for a software per administration.
If we want to keep it the way it is (possibility for multiple uses), I suggest we should add a new select when, in the form, a user select an administration, so they can choose which use to update or to create a new one. This will require some more work, but will make all the uses available for modification, and improve the auto-fill of the fields to display the selected use instead of defaulting to the first one.
I think it makes sense that an administration could be using the same software for multiple use cases and sometimes it could event be different teams within that organization (so different contacts).
Anything that can simplify the form for the user I think is good!
However, I just found out that the way we update the data overwrite any use that is not the selected use we update with the form, so it only keeps one in the pull request.
It should be a fix for it since the form now sends an array of uses instead of just one
