| A Curam participant or user must be selected as the Incident Participant. | Link | No | |
| An entity identifier cannot be null. | Link | No | |
| An Exception occurred as the timeout has been reached and the transaction has been rolled back. | Link | No | |
| An Incident must be set for Incident Participant. | Link | No | |
| An Incident Participant can not be both a Curam participant and user. | Link | No | |
| An Incident Participant role can not be created because it can not be determined if the participant selected is a duplicate. Embedded message: '%1s'. | Link | No | |
| A reporter can not be recorded for an anonymous incident. | Link | No | |
| A row identifier cannot be null. | Link | No | |
| More than entity of type '%1s' with key value '%2s' found in the cache. | Link | No | |
| No database access is allowed at this point. | Link | No | |
| No security implementation is supported for this transaction type. Please contact an Administrator. | Link | No | |
| Role must be entered. | Link | No | |
| Status must be entered. | Link | No | |
| The login ID %1s does not map to a user name. | Link | No | |
| The participant already has a role of this type on the incident. | Link | No | |
| The participant is marked as a duplicate and their details cannot be edited. The correct person should be added to the incident and the duplicate removed. | Link | No | |
| There can only be one active reporter for an incident. | Link | No | |
| The user already has a role of this type on the incident. | Link | No | |
| You cannot modify this record as it has been canceled. | Link | No | |
| You do not have access to this incident's details. | Link | No | |
