Exit Points have logic in them to automatically populate Event parameters if the Event parameter is named a specific way. If you are creating your own Event and want to use the auto-populate feature, create and name the corresponding Event parameters exactly as listed here.
Note: All Exit Point Event Parameters are case-sensitive.
| Inbound Acknowledgement Error | |
|---|---|
| payload | The data, or payload, passed to the Event. This data is attached to the email. |
| interchangeProperties | A list of ISA values |
| acknowledgementErrorProperties | The acknowledgement |
| Inbound Duplicate Interchange | |
|---|---|
| payload | The data, or payload, passed to the Event. This data is attached to the email. |
| interchangeProperties | A list of ISA values |
| Inbound EDI Route Error Handler | |
|---|---|
| payload | The data, or payload, passed to the Event. This data is attached to the email. |
| interchangeProperties | A list of ISA values |
| routeErrorList | An array of the route errors that occurred |
| Inbound EDI Route Not Found | |
|---|---|
| payload | The data, or payload, passed to the Event. This data is attached to the email. |
| interchangeProperties | A list of ISA values |
| routesNotFoundCount | A count of the number of routes not found |
| Inbound EDI Route Process Binding Not Found | |
|---|---|
| payload | The data, or payload, passed to the Event. This data is attached to the email. |
| interchangeProperties | A list of ISA values |
| routeProcessBindingsNotFoundCount | A count of the number of process bindings not found |
| Inbound Interchange Processed | |
|---|---|
| payload | The data, or payload, passed to the Event. This data is attached to the email. |
| interchangeProperties | A list of ISA values |
Comments
0 comments
Please sign in to leave a comment.