Infor Business Context in GenAI agent

Infor Business Context (IBC) is an Infor OS feature that allows Infor applications operating within the Infor OS Portal to share information about the current screen.

IBC is designed to provide a dynamic context of the user’s actions to other applications running in the portal. The GenAI Assistant uses IBC messages to input variables for the agents and tools. When a user navigates to a screen in the CloudSuite application that publishes the IBC message to the Infor OS Portal, the GenAI platform receives this message. Once received, it is accessible to any agent within the current session. If users inquire about an item on the screen, the GenAI Assistant selects the appropriate agent to handle the query and obtain the agent's Logical ID (LID) prefix. The agent then compares its LID prefix with the IBC LID prefix. If they match, the agent gains access to the IBC message and is responsible for parsing the information on the entities and matching any required input variables for the tools. In the absence of a match, the agent prompts the user for the necessary details to invoke the tools and complete the task.

Configuring the IBC in Agent

To use IBC messages, the agent must be associated with the Logical ID Prefix of the application sending the message and have a clear instruction on which properties from IBC message must be used. This configuration is run during Agent creation or edit in the GenAI Factory. While IBC messages and payloads enhance the user experience, they are optional. Agents must function independently of the IBC and its payloads.

To associate the IBC payloads with the Agent, first go to the agent's details page and select the Logical ID of the application from the menu. Next, update the instruction to outline how to use IBC payloads.

Note: To disregard IBC functionality and revert to pre-IBC operations, remove the Logical ID Prefix association from the agent.

Example for the Agent description to use the IBC Message: "This Agent needs a company ID, which can be retrieved from the <FetchCompanyIdTool> or the first entity in the IBC payload if available."

IBC payload

Use this example to ensure you understand the required details for configuring IBC messages:

From this JSON provide me the JSON navigation to the id when "entityType" is equal "OIS100A": {
  "logicalId": "lid://mm.mm.m",
  "screenId": "m3_OIS100_A",
  "supportProductId": "109562",
  "program": "OIS100",
  "panel": "A",
  "screenIdBase": "OIS100",
  "entities": [
    {
      "entityType": "OIS100A",
      "id1": "OACONO880OAORNO ",
      "drillbackURL": "?"
    }
  ],
  "contextId": "OIS100_175611230076124",
  "guid": "d9738812-7898-4ce2-9330-29131cec82cd",
  "date": "2025-07-25T17:23:35.216967Z"
}
$.entities[?(@.entityType==”OIS100A”)].id1