Troubleshooting — Commit failure.. unique constraint violated |
When a user attempts to create a work object, the object is not created and an error message appears.
The system attempted to create a work object ID for the new work object that matched an existing work object ID in the same application.
This may occur when an application (and its work pool) is used by an operator who belongs to a different organization than other operators who have previously used the application (and its work pool).
To diagnose which organizations have used which work pools, use the Class Explorer to list instances of the Data-UniqueID class.
1. If the operator encountering the error is not intended to use this application, update the access group and application rules as necessary to correct the RuleSets and work pools available to the operator.
2. If the operator encountering the error is to use the application, but is recorded as part of the wrong organization, open and update the Operator ID data instance.
3. If a single application is intended to be used (separately) on one Process Commander system by operators who are in different organizations, you must create separate work pools, separate Database Table instances and separate work object types for each.
4. If your application has unusual application requirements, your application can override the standard work object ID numbering scheme, defined through two activities named GenerateID.
Work object ID | |
Understanding work object IDs |