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.

Reporting date

2015-07-21

Reported by

Robert Cerny

Resolving date

2022-11-05

Resolved by

Robert Cerny

Resolved in version

Topincs 9.2.0

Blocked by

Add server side validation(Enhancement)

Related to

Unique value constraint for service(Change)

Work sessions2

5254

11419