Sync tables set the framework conditions and the content of the change notification.

1. Go to the  Administration tab in the function bar and select  Settings >  Synchronisation.
2.  Add a new Sync. Table and select  Notification at xx.
   Note: The available Sync. Server will be offered for selection.
3. Enter a unique, speaking Name for the sync table or use the server name (recommended).
4. Select the data source from the picklist.
   Note: Only data with a date or time reference are available.
5. Assign the export list (Type: Info Centre list).
6. Enter a time range in minutes as Export delay. This time determines how long after saving a record the change notification will be sent.
   Note: Make sure that the server, name, data source, export list and text template have the same objectives.
7. Make the following settings:
   a) Notify responsible users / user group
   Only the Sync Server accounts of type user or user group are notified. Each user account only receives the data relevant to them.
   Example: User "Smith" only receives notifications about changes to appointments that affect them as participant or responsible.
   b) Notify staff members individually
   Only the Sync Server accounts of type "Staff member" are notified.
   Example: User "Smith" receives change notifications for their own shifts.
   c) No selection Only the sync server accounts of type "Sync server account" and "Distribution list" are notified. These can be used to notify stakeholders who are not Bp Event users.
   Example: Event changes are communicated to various departments and an external caterer.
8. Set as the number of days before the reference date (e.g. event date) that the notification should be sent as Notification lead time.
   Example: With a lead time of 14 days, recipient will not be notified of any changes made three weeks before the event. This reduces the information load.
9. The Max. failed attempts defines how often the notification function may fail before execution is cancelled.
10. Select a Text template for the notification text.
11. Select attachments in the Data sheet as email attachment field, such as updated worksheets (created as text data sheet) for an event.
12. Tick Attach ICS files to include calendar entries in the attachment.
    Example: The event date has been postponed, an updated calendar entry is included in the email.
    Note: The form and content of the calendar entry cannot be customised.
13. To log whether a notification has been sent in the change history of the record, tick Log to record.
    Note: Logging may generate a large amount of data and should be selected with care.
14. Click on Discard data and reload in the event of changes, e.g. in the text template or the export list of the Info Centre type, to avoid triggering a change notification for all affected records.
    Note: All changes are reloaded (reset) without triggering change notifications. Please use with caution.
15. Show synchronised data is used during setup or error analysis. Calls up a list of all records affected by changes and provides information on synchronisation.
16. Show unsynchronised data lists all changes that can trigger a notification during the next synchronisation, provided they qualify for the notifications (job).
    Note: Neither the export list (Type: Info Centre list) nor the number of days for the notification are considered here.
17. Test export list with unsynchronised data can be used for testing during setup.