Using the BOD mappings detail view
Use the BOD Mappings detail view to manage the Business Object Document, or BOD, mappings defining the information transfer between the host system of records and the subscriber, Infor CRM SLX. See Back Office
The system administrator and users with the appropriate role can access these features. See What are Roles and Secured Actions?
You can click the BOD Mappings tab, and click the required BOD mapping name in the Back Office detail view, to access the BOD mapping detail view.
On this page you can:
- View an out-of-the-box read-only upgrade safe Bod Pack based BOD Mapping record.
- Edit a customized BOD Mapping record. (Customization of a BOD Mapping record is accomplished via the Back Office detail view BOD Mapping tab.) link in the
Information fields
The information fields contain the primary information about the BOD mapping record. Some information can be edited, however other information cannot be added after the BOD mapping is created.
Field | Description | Can be edited? |
---|---|---|
Back Office | The back office associated with the BOD mapping. | No |
BOD Mapping | The display name of the BOD mapping. | Yes |
Noun | The noun, as defined by the BOD standard, to be processed by the BOD Mapping record. For example, CustomerPartyMaster, ContactMaster, Quote, SalesOrder. A given Back Office can have one and only one BOD Mapping record for a given noun. | No |
Entity | The Infor CRM SLX entity, or record type, being mapped. | No |
Inherit Owner From | Designates the parent entity from which the mapped entity inherits
ownership. Ownership is inherited from the related Account in most
cases. Click the drop-down arrow and select from the list. |
Yes |
Delete Behavior | Specify the required Infor CRM SLX
action for inbound Sync BODs with an action code of DELETE. Possible values:
The integrated content deleted in Infor CRM SLX, from the user interface, always soft deletes the content and then publishes the delete request to the host system. |
Yes |
Handler Class |
Use this field to specify a custom handler. A custom handler is a fully qualified name of a user-defined
C# class replacing the generic anyBod handler. See
|
Yes |
Unique ID XPath | The BOD XPath for the unique ID value published by the host system of record. | Yes |
Unique ID Node | Sample unique ID BOD element and corresponding element attributes. | Yes |
Active | Use this option to turn on or turn off synchronization for this BOD mapping. | Yes |
Custom | Identifies custom BOD mappings. | No |
Outbound On Create |
Determines promotion of new data from Infor CRM SLX to the back office. Includes the automatic promotion of dependent entities when they are related to a promoted account.
|
Yes |
Outbound On Update |
Determines promotion of updated data from Infor CRM SLX to the back office once the content has been successfully promoted. Possible values:
|
Yes |
Outbound On Delete | Determines
promotion
of deleted data from Infor CRM SLX to the back office once the content has been successfully
promoted.
Possible
values:
|
Yes |
Generate Outbound Template | When selected, Infor Infor CRM SLX
regenerates the outbound template based on BOD field mapping
updates. This option must be cleared if the outbound template is manually modified. = |
Yes |
System of Record | Select the application to use as the
system
of
record.
Options are Back Office or CRM.
|
Yes |
To save any changes, click
.Detail view tabs
Each tab shows specific information you can use for BOD mapping related activities. Click a link to see more information about each tab.
- Field Mappings. See Field Mappings Tab
- Custom Field Mappings Tab. See Custom Field Mappings
- Acknowledge Template. See Acknowledge Template
- Process Template. See Process Template
- Sync Template. See Sync Template