Enhancement
Better handling of modeling errors
Issue description
Currently the system throws a ModelerException when the administrator makes an error E. This happens on the next request that generates the constraints after the schema cache was cleared. In a productive system this renders the system unusable as long as E is not corrected. This is not acceptable and should be changed. Either disallow the saving of the form causing E or create a page which shows all modeling errors, but all system fragments unaffected by the error remain functional.
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.