Bug
Duplicate constraint declaration causes strange form behavior
Issue description
When a user makes a change in a form field, it usually saves. Not so if there is two topic occurrence constraints declared on a topic type (e.g. directly and at a super type). Then the user edits the form field and nothing is changed when saving. Topincs does not recognize the change because it the form field is rendered twice due to the duplicate constraint declaration. Throw a modeling error in this case.
Developer comments
Topincs throws an %ModelerException% now indicating the sername collision.
|
Work sessions2
Start |
2019-10-26T07:32:45
|
End |
2019-10-26T08:25:53
|
Participant |
Robert Cerny
|
Start |
2019-10-26T09:57:42
|
End |
2019-10-26T10:29:17
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.