BOD Mappings tab

Use the BOD Mappings tab to view and manage the Business Object Document, or BOD mappings defining the information transfer between the host system of records and the subscriber, application. See Back Office

Note: The system administrator and users with the appropriate role can access these features. See What are Roles and Secured Actions?

To access the BOD Mappings tab, you can click BOD Mappings tab on the Back Office detail view. See Using the Back Office detail view

On this page, you can:

  • Click the BOD Mapping to view the BOD Mapping detail view. See Using the BOD mappings detail view
  • Add a BOD mapping:
    1. Click Add New Mapping icon.
    2. Follow these steps for adding a BOD mapping. See Adding a BOD mapping (back office extension)
  • Modify BOD mappings:
    1. Select Customize or Edit to modify the BOD mapping content.
    2. Select the BOD mapping name to access BOD mapping detail view. (Customized BOD mappings can be modified in the BOD Mapping detail view.
    3. Content is not modifiable in the BOD mapping tab grid.

This view contains the following columns:

BOD Mapping

The name of the BOD mapping and a link to the BOD Mapping detail view.

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 noun can be defined by one and only one BOD Mapping record for a given Back Office.
Entity
The application entity, or record type, being mapped. Specify the name of an application entity type. For example, Account or Sales Order.
Priority
Specifies the order in which BODs are processed. Specify any 3-digit number to designate the BOD Priority. The BOD with the lowest number are processed first and all other BODs can be processed in ascending order.
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 any Bod handler. See Saleslogix.Integration.BOE.Jobs.Message.ItemMasterHandler.
Active
Use this option to turn on or turn off synchronization of customized BOD mappings.

To undo any changes, click Reset before clicking Save.

System of Record
Identifies which system is the authoritative data source for certain record types in an integration. This is the system that publishes and maintains the master copy of the data content. The subscriber system consumes the published data. The subscriber system can request the system of record to create or update data, but those requests are subject to the system of record’s standard business rules.

For example, the system of record determines the direction in which BODs are sent. Sync BODs are published from the system of record to the subscriber application, Process BODs are sent from the subscriber application to the system of record, and Acknowledge BODs are sent to the subscriber application by the system of record in response to Process BODs.

Outbound On Create
Determines promotion of new data from application to the back office. Includes the automatic promotion of dependent entities when they are related to a promoted account. See Promote to back office
  • (A) Automatic - Promotion and updates are automatically published to the integrated back office application. Requires no action by the user.
  • (U) User Triggered - Promotion and updates are published to the integrated back office application only after the user clicks the Promote task in the Task Pane.
  • (D) Disabled - New content can not be published to the integrated back office application.
Outbound On Update
Determines promotion of updated data from application to the back office once the content has been promoted to the integrated back office application.
  • (A) Automatic - Updates are automatically published to the integrated back office application. Requires no action by the user.
  • (U) User Triggered - Updates are published to the integrated back office application only after the user clicks the Promote task in the Task Pane.
  • (D) Disabled - Updates can not be published to the integrated back office application.
Outbound On Delete
Determines promotion of deleted data from application to the integrated back office application.
  • (A) Automatic -Deletions are automatically published to the integrated back office application. Requires no action by the user.
  • (U) User Triggered - Deletions are published to the integrated back office application only after the user clicks the Promote task in the Task Pane.
  • (D) Disabled - Deletions are not be published to the integrated back office application.