...
| EventCode | Context | ErrorMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| everywhere | Several | Code used for multi purposes: Mostly for debug messages below level warn, where no fixed message is needed. | ||||||
| everywhere | Several | Default code used for old error messages, which are not converted yet to the new error code system. | ||||||
| everywhere | Log HTTP Request | The HTTP request to the server and its parameters are logged. Generally for debugging only. | ||||||
| entities | Duplicate Key | A database key for the entity to be saved does already exist. | ||||||
| entities | Integrity Constraint Violation | An entity can not be added or updated since a referenced entity does not exist (anymore). Or an entity can not be updated or deleted since it is referenced by other entities. | ||||||
| everywhere | HTTP Status 404 | The requested URL / page was not found, the API endpoint in the application does not exist. | ||||||
| everywhere | HTTP Status 422 | The PUT / POST request to that URL could not be processed due invalid given data. The invalid fields are listed in the result from the server. | ||||||
| everywhere | HTTP Status 422 | The File Upload did not succeed PUT / POST request to that URL could not be processed due invalid given data. The invalid fields are listed in the result from the server. | ||||||
| everywhere | HTTP Status 409 | The PUT / POST request to that URL could not be processed due the given data would produce an invalid state of the entity on the server. If possible, the causing fields are listed in the result from the server, or the error message is self explaining. | ||||||
| everywhere | PHP Fatal Error | PHP Fatal error, see error message for details. | ||||||
| everywhere | PHP Warning | PHP Warning, see error message for details. | ||||||
| everywhere | PHP Info | PHP Info, see error message for details. | ||||||
Users & Customers
| EventCode | Context | ErrorMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Customer | A client cannot be deleted as long as tasks are assigned to this client. | Remove all tasks first from that customer. | ||||||
| User | The user can not be deleted, he is PM in one or more tasks. | Change the PMs in the affected tasks. |
Task & Workflow
| EventCode | Context | ErrorMessage | Description / Solution | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Task; Workflow | Multi Purpose Code logging in the context of a task | Multi Purpose code for several info logs around a task. Also important in Context of workflow. | ||||||
| Job; Workflow | Multi Purpose Code logging in the context of jobs (task user association) | Multi Purpose Code logging in the context of jobs (task user association) | ||||||
| Workflow only | Multi Purpose Code logging in the context of pure workflow processing | Multi Purpose Code logging in the context of workflow processing | ||||||
| Task | The task can not be removed due it is used by a user. | One user has opened the task for reading or editing the task. Therefore this task can not be deleted. | ||||||
| Task | The task can not be removed due it is locked by a user. | One user has opened the task for editing the task, or some other action has locked the task. Therefore this task can not be deleted. | ||||||
| Task | The task can not be locked for deletion. | The task must be locked by the deleting user, before it can be deleted. This lock could not be set. | ||||||
| Task; ManualStatusCheck Plug-In | The Task can not be set to finished, since not all segments have a set status. | Each segment must have set a status in order to finish the task. | ||||||
| The current task status does not allow that action. | This error occurs if the current status of the task does not allow the triggering action. |
...