Creating Custom Calendar Fields

9-6 Administrators Guide for Oracle Business Data Synchronization Server with the calendar record. Further, assume that the administrator wants to synchronize this field to a field in Exchange. Since there is no ICAL field that can represent this field, define a custom ICAL field, such as X-ORACLE-BDSS-BPEL-HTTP-LINK. You then modify the Hub XSD to have a ICAL X- field, such as X-ORACLE-BDSS-HUB-HTTP-LINK, and then map the two fields in the Hub-To-PIM and PIM-To-Hub XSLs used by the BPEL Task Connector. To synchronize the field to Exchange, define an Exchange custom ICAL field, such as ORACLE-BDSS-EXCHANGE-HTTP-LINK and map it to the ORACLE-BDSS-HUB-HTTP-LINK field in the Hub-to-PIM and PIM-to-Hub XSL used by the Exchange connector. When defining the Exchange custom field in the Exchange XSD, you can define it as an extended field or an unindexed field. Writing the HTTP Link to the Location field on the Exchange calendar, define the field as the Exchange unindexed field Location. Because this unindexed field is naturally mapped to the ICAL LOCATION field, the connector uses the ORACLE-BDSS-EXCHANGE-HTTP-LINK value instead of the ICAL LOCATION value to update the Location field, the BPEL Task Connector overwrites the field during subsequent synchronization sessions to which it naturally maps the ICAL LOCATION field with the link if the change comes from Exchange. If the connector uses the ICAL LOCATION field and ignores the ORACLE-BDSS-EXCHANGE-HTTP-LINK value to update the Location field, then a subsequent session results in the BPEL Task Connector deleting the HTTP Link field value if the change originates from Exchange. If you defined the field as an Extended Field that specifies a custom field that is, it would remain hidden unless you define an Outlook custom form that would expose the field in the Outlook UI, then this form of data loss would not occur. Note: In this example, the BPEL Task Connector would not hard-code this customization by specifying the HTTP Link value as the LOCATION field value when it builds the ICAL that is sent to the Hub. Part III Appendixes This part contains the following appendixes and a glossary: ■ Appendix A, BDSS Configuration Operations ■ Appendix B, Configuring the BPEL Task Connector ■ Appendix C, Tables in the BDSS Data Stores ■ Appendix D, Connector API ■ Appendix E, Custom Field XSLTs and XSDs ■ Appendix F, Troubleshooting BDSS ■ Glossary