Page: View Communication Exception
| This page allows you to view a participant communication exception. A communication exception is used to indicate that a participant does not wish to receive communications from the organization in the format specified. If a correspondent has an active communication exception, a communication cannot be created using that method. |
|
Click the diagram to manipulate and zoom. Traverse the diagram using
Click-and-Drag motions.
| Fullscreen |
|
|
| Details |
| Label | Type | Description | Mandatory |
| Method | COMMUNICATION_METHOD_CODE | Method of communication that you cannot use to contact the participant. | No |
| Reason | COMM_EXCEPTION_REASON_CODE | Reason why you cannot use the above mentioned method of communication. | No |
| From | CURAM_DATE | Period of time from which the communication exception applies to the registered participant. | No |
| To | CURAM_DATE | Period of time to which the communication exception applies to the registered participant. | No |
| Status | RECORD_STATUS_CODE | The status is "active", unless the record has been deleted, in which case, the status is "canceled". | No |
|
| Comments |
| Label | Type | Description | Mandatory |
| Comments | COMMENTS | User comments on this record. | No |
|
| When page is loaded |
| Message | Message Catalog | Configurable | Configurable Validation Reference ID |
| An Exception occurred as the timeout has been reached and the transaction has been rolled back. | Link | No | |
| No security implementation is supported for this transaction type. Please contact an Administrator. | Link | No | |
| The login ID %1s does not map to a user name. | Link | No | |
|
| When page is submitted |
| None |
|
|
|
| When page is submitted |
None |
|
