Details
Description
Current behavior
When someone submits a user (or group) which does already exist, then a SQL Integretiy Constaint Violation Exception is thrown.
Desired behavior
Since this is effectively a validation error, it would be better if the user would get a more appropriate error.
Example Error:
Server Error : ENGINE-03004 Exception while executing Database Operation 'INSERT UserEntity[test]' with message ' ### Error updating database. Cause: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (XYZ.SYS_C00231904) violated ### The error may involve org.camunda.bpm.engine.impl.persistence.entity.UserEntity.insertUser-Inline ### The error occurred while setting parameters ### SQL: insert into ACT_ID_USER (ID_, FIRST_, LAST_, EMAIL_, PWD_, SALT_, REV_) values ( ?, ?, ?, ?, ?, ?, 1 ) ### Cause: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (XYZ.SYS_C00231904) violated '. Flush summary: [ INSERT UserEntity[test] ]
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
- is related to
-
CAM-9189 Prevent communication error message for duplicated user / groups
-
- Closed
-