ION Connect and BOD Event Architecture
Infor ION Connect is the middleware layer that routes business events between CloudSuite Industrial and external systems. When a SyteLine user creates a customer order, ships a product, or posts a journal entry, SyteLine publishes a standardized BOD (Business Object Document) to the ION messaging infrastructure. BODs follow the OAGIS (Open Applications Group Integration Specification) standard and include a Verb (Sync, Process, Acknowledge) and a Noun (SalesOrder, Shipment, JournalEntry) that describe the event.
You configure Data Flows in ION Connect to route specific BODs to your webhook endpoint.
- BOD structure: Verb + Noun pattern (e.g., Sync.SalesOrder, Process.Shipment, Acknowledge.PurchaseOrder)
- Configure document flows in ION Connect: Application > Connection Point > Document Flow > Routing
- Create an API Connection Point for your webhook: specify the endpoint URL, authentication, and HTTP method
- Map BOD nouns to document types: Sync.ItemMaster routes item changes, Sync.CustomerPartyMaster routes customer updates
- Enable BOD publishing in SyteLine: verify the ION Desk > BOD Mapping configuration for each transaction type
Building a Webhook Receiver Endpoint
Your webhook receiver must accept HTTP POST requests containing BOD XML or JSON payloads from the ION Gateway. The endpoint should validate the request authenticity using the shared secret or certificate configured in the ION Connection Point. Process the incoming BOD by parsing the Verb and Noun to determine the event type, then extract the business data from the DataArea element.
Respond with a 200 OK within 30 seconds to prevent the ION Gateway from retrying the delivery. For long-running processing, acknowledge the webhook immediately and process the data asynchronously using a message queue.
- Endpoint requirements: HTTPS, POST method, responds with 200 OK within 30 seconds, handles BOD XML/JSON
- Validate authenticity: check the X-ION-Signature header against your shared secret using HMAC-SHA256
- Parse BOD payload: extract Verb, Noun, BODID, and DataArea containing the business entity properties
- Async processing: enqueue the BOD payload to RabbitMQ, Azure Service Bus, or AWS SQS for background processing
- Idempotency: use the BODID as a deduplication key to prevent processing the same event twice on retries
Monitoring and Troubleshooting Event Delivery
ION Connect provides visibility into event delivery through the ION Desk monitoring console. The Data Flow Monitor shows the status of each configured flow, including message counts, delivery successes, failures, and retries. When events fail to deliver, ION queues them in a dead-letter store for manual reprocessing.
Common delivery failures include webhook endpoint timeouts, authentication errors, and malformed response codes. Set up alerts in ION Desk for delivery failure thresholds so your team can investigate and resolve issues before the dead-letter queue grows too large.
- ION Desk monitor: navigate to ION Connect > Data Flow Monitor to view real-time event delivery status
- Dead-letter queue: failed events appear in ION Connect > Errors with the failure reason and original payload
- Retry policy: ION retries failed deliveries 3 times with exponential backoff before moving to dead-letter
- Alert configuration: set up email alerts in ION Desk when delivery failure count exceeds threshold per hour
- Test event delivery: use ION Connect > Test Document Flow to send a sample BOD to your webhook endpoint
Try it here, free
SyteLine AI Integration Readiness Assessment
Score your SyteLine environment across version, IDO and ION API maturity, data quality, integration middleware, and organizational readiness for an AI layer.
Netray AI agents design and implement event-driven SyteLine integrations using ION webhooks and BOD subscriptions. Replace fragile polling patterns with reliable real-time data flows.