Sharing business object data
When the connection between the external system is established, the business objects whose data is going to be exchanged must be mapped.
This means that for each individual record in Planon (recognized by its business object type and system code) the External ID for the communication with the external system needs to be registered in the External BO links business object.
This can be done by an app that uses the IExternalBOLinkService service interface to populate the External BO links level.
Using an app
An app is built to monitor and synchronize the BO data for which it is designed to be used. Exactly which information this is, is included in the app. Between the systems that are sharing business object data there now is an understanding about this data.
Example
The following use case describes how an app can be used to share business object data.
 | Apps can be implemented by Tailor Made Solutions (TMS) or partners. For more information, see developing platform apps. |
System A is responsible for maintaining System B's assets.
1. A new order is created in System B.
This is detected by the app, which will sync the BO data and share that with System A.
| | The exchange takes place using Event Connector. Message sent, must always include the external ID, which is used to identify the BO in the external system. |
2. When a request is created in the System B for an asset, an order is created in System A.
3. Once the order is completed by System A, the data is synced with System B.