How to add AI agents to Infor SyteLine

Infor SyteLine (CloudSuite Industrial) integration surface

• IDOs through the Mongoose IDO runtime: the Load Collection request returns rows from an IDO with filter and property lists, and IDO methods run business logic. On Infor OS / cloud deployments this is typically reached through the ION API gateway with OAuth service accounts; on-prem installs expose the IDO web service directly (REST and, in older versions, SOAP). Check the endpoint style your version supports.
• The SQL Server application database. Tables carry the _mst suffix (for example item_mst, job_mst, jobmatl_mst, po_mst, poitem_mst, co_mst, coitem_mst, matltran_mst) and almost every row has a site_ref column because SyteLine is multi-site. A read-only replica or a reporting login is the safest source for broad analytic reads.
• The Application Event System (AES): event handlers fire on IDO events and can call actions, including a web request. This is the clean way to trigger an agent when a record changes without polling.
• ION and BODs: where the customer has Infor ION, SyteLine publishes and consumes BODs for documents such as purchase orders and sales orders. BODs are a decoupled way to receive change notifications.
• Utility and background features: scheduled background tasks, report requests, and user-defined methods (custom IDO methods written in .NET) that can wrap tricky logic so the agent calls one safe method instead of many.

How it works

1. 1

   Pick one workflow and define done

   Choose a task with a clear input and a reviewable output, such as drafting expedite emails for late POs. Write down what the agent may read, what it may propose, and what a human must approve.

2. 2

   Create a dedicated SyteLine user

   Make a service user with the minimum authorizations for the forms and IDOs involved. The agent inherits that user's rights, so SyteLine's own security remains the boundary.

3. 3

   Build a thin tool layer

   Wrap each capability as a narrow function: get_open_po_lines, get_job_material_status, get_item_availability. Each tool calls an IDO load or a parameterized query and returns compact JSON, never raw SQL access for the model.

4. 4

   Add write tools as drafts

   Writes create something reviewable: a planner note, a requisition, a change request record, or an email draft. If a direct IDO write is justified, run it only after an explicit approval step and log the payload.

5. 5

   Wire triggers

   Use an AES handler, a ION BOD subscription, or a scheduled job to start the agent. Pass only record keys; let the agent fetch current data through the tools.

6. 6

   Add evaluation and logging

   Store every prompt, tool call, result, and approval. Replay a sample of past exceptions with known answers before going live, and review a weekly sample afterward.

Security checklist

• Use a dedicated SyteLine service user and give it only the authorizations the workflow needs.
• Expose tools, not SQL: the model should never write its own queries against production tables.
• Require human approval for any write to orders, purchasing, inventory, or financial records.
• Log every tool call with user, parameters, row counts, and timestamp, and keep the log outside the agent service.
• Restrict outbound network access from the agent host, and scrub credentials from prompts and logs.