Bug
Service formal name not checked for uniqueness
Developer comments
There is no Unique value constraint on the corresponding name type.
The topic type _Service_ shares the name type _Formal name_ with the topic type _Event type_. A number of names are thus not open for services given a unique value constraint is introduced.
A unique value constraint requires an update of the system topic map, thus the move away from the bugfix release.
Implemented by throwing a StateException, so a modal window pops up in the form to inform the user. Can be improved later by server side validation, which would show the error message directly at the form field.
|
Work sessions2
Start |
2015-08-18T07:27:44
|
End |
2015-08-18T07:43:51
|
Participant |
Robert Cerny
|
Start |
2022-11-05T13:35:24
|
End |
2022-11-05T14:06:57
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.