BOD integrations

An outbound operation typically begins when a user performs an action in Optiva that requires a data exchange with another ION-enabled product. A Business Object Document (BOD) XML message is generated by Optiva and placed in an area designated as the Optiva message outbox. At scheduled intervals, ION connects to the outbox and retrieves the BODs from it.

In ION Desk, a connection point is set up for each product or site in the CloudSuite that can send or receive BODs. If you add products later, the Infor Cloud team adds connection points for them, as needed. The connection point defines the information needed to connect to the application database. It also holds a list of all the BOD documents that the application can send or receive.

You define document flows between the connection points to represent the business flows between the products. For example, the Infor Cloud team sets up a document flow between Optiva and Infor Ming.le to pass BODs that contain user and role information. Use the Modeler in ION Desk to define these document flows.

ION routes BODs according to the document flows between BOD-enabled products. If a document flow is defined from Optiva to another product for a particular BOD, then at specified intervals, ION places the outbound BOD from Optiva in the other product’s designated message in-box. Products are responsible for validating and incorporating the data in inbound BODs according to their rules.