Configuration and requirements

CRM.connector lets you define further synchronization criteria.

Here's a list of synchronization criteria that your administrator can define:

• The users in the groupware system and update.CRM whose data should be synchronized automatically.
• Which contact types in update.CRM should be synchronized.
• Whether private appointments and e-mails should be synchronized.
• The time period over which appointments, tasks and e-mails should be synchronized (e.g. two weeks in the past, four weeks in the future).
• The interval in which new records should be synchronized (e.g. every 15 minutes). Calendar elements, tasks and e-mails can be synchronized in different intervals.
• Whether attachments are synchronized.
• Whether participants that cannot be (uniquely) identified are marked for subsequent editing, or whether these participants are entered in the text field.
• Whether appointments only involving internal reps are indicated as such.
• Which additional fields (e.g. address fields in contact addresses) are synchronized
• Whether data deleted in update.CRM is also deleted in the database, or only marked as deleted.
• Whether appointments organized by an external participant are published to update.CRM, so that these time slots are marked as busy.
• Whether appointments are only synchronized if they are added in update.CRM (unidirectional). Appointments added in the groupware system are not synchronized. Changes made to previously synchronized appointments are synchronized in both systems (bidirectional).

Requirements

Records in the groupware system (e.g. calendar elements or e-mails) can be transferred to the update.CRM database as contact records if the following requirements are met:

• The groupware user must be present in the update.CRM database as both a person and rep.
• The same e-mail address must be entered in both records. This e-mail address must be unique.