COR_OUTBOX_ENTRY
This table shows the COR_OUTBOX_ENTRY table API:
| COR_OUTBOX_ENTRY | Description |
|---|---|
| C_ID | The row's primary key - all of the provided database schemas have this set as auto-increment. |
| C_XML | The message that you are sending. The message must be encoded as described below. |
| C_TENANT_ID | The Tenant Id identifies the message as belonging to a specific tenant. A tenant is a hosting or software as a service (SaaS) concept where all the data for one tenant is always separated from all the data of other tenants. There is no cross-sharing or viewing of data with other tenants. This concept requires all the participants in the messaging to share the same identity for the same tenant. Therefore, a Tenant ID of " infor " must have exactly the same meaning on every system in the messaging space. |
| C_LOGICAL_ID | This field is added since ION 11.1.2. It is added by running the scripts present in the '3.0' folder in your inbox/outbox. If present, then this field must contain the value of the 'from logical id' of the application that publishes the BOD and it must be populated with the ‘lid://’ prefix. |
| C_MESSAGE_PRIORITY | Messages with a higher priority are sent before messages with a lower priority. You can set the priority from 0 to 9, 9 being the highest priority. High priority messages should be limited - most messages should be set at 4. |
| C_CREATED_DATE_TIME | The date and time the message was inserted into the outbox table. You must specify the time in the variable in UTC format. |
| C_WAS_PROCESSED | Users should never provide a value for this column. The column is used by ION Service to determine whether a message has been sent. Unprocessed messages are marked as 0; processed messages are marked as 1. |
ION Service removes all the processed messages older than the number of hours specified in the cleanup advanced properties.