Terminology
This table shows the terms and definitions related to User BODs:
| Term | Definition |
|---|---|
| BOD | Business Object Document. File containing application or user data used to
transport the data between systems and applications. Infor OS User Management Interface within Infor OS Portal (or Infor Ming.le) where user data is created and managed. |
| Connection Point | Connect Infor applications, databases, message queues, and files. In this instance refers to the physical database where ION sends or retrieves BODs. Each application that sends BODs should have a connection point defined. |
| IOBox | The physical database that holds incoming (I) and outgoing (O) BODs. |
| Data flows | Event-driven sequence of activities that send or receive documents. They typically represent a business process. Contains at least two connection points. Where you define what BODs will be sent and received by each connection point. |
| GUID | Global User ID. Alpha numeric ID used to track users across all systems. Typically associated with the primary authentication service on a system. |
| Logical ID | URL formatted indicator for the system that generated or will consume the BOD or information within the BOD. Created based on information in the connection point for the application. |
Types of User BODs
This table shows the types of User BODs and the to/from information for each type:
| Type | Information Sent to/from |
|---|---|
| Process.SecurityUserMaster | Sends user changes from an application to IFS |
| Sync.SecurityRoleMaster | Sends role changes from an application to IFS |
| Sync.SecurityUserMaster | Sends user changes from IFS to applications |
| Acknowledge.SecurityUserMaster | Sent from IFS to applications to acknowledge a change made to a user in an application was processed in IFS |