Functional scope
Learn about the details, limitations and restrictions of Connector SE.
Appointments
| Bi-directional synchronization of appointments, where the chair is a synchronization user | YES | ||
|
Details, Limitations and Restrictions |
recurring appointments 1 |
from groupware system to Aurea CRM | YES 2 |
| from Aurea CRM to groupware system | YES | ||
| external appointments (appointments generated by "external persons") | YES ("published" 3 ) | ||
| appointments, where the chair is not a synchronization user | YES ("published") | ||
| synchronization of participants | YES | ||
| synchronization of participants invitation status | YES,requires 8.1.6.5855 or higher | ||
| Linking ofappointments to additional info areas 4 | NO | ||
|
synchronization of Attachments |
from groupware system to Aurea CRM | YES | |
| from Aurea CRM to groupware system | NO | ||
| deletion of appointments | YES, bi-directionally 5 | ||
| Turning on/off synchronization of Private appointments | YES 6 | ||
| Synchronization of additional of additional fields 7 | YES | ||
| Manual linking to companies/persons | NO, it’s a server application | ||
E-Mails, contact persons, tasks and absences
| synchronization of e-mails from groupware system to Aurea CRM | YES | |
|
Details, Limitations and Restrictions |
Synchronization of attachments | YES |
| Serialization of e-mail in original mail format | YES (*.msg file) | |
| Synchronization of Drafts | NO | |
| Synchronization of additional fields | NO | |
| Linkingof e-mails to another info area 8 | NO | |
| contact persons | ||
| Synchronization of contact persons from Aurea CRM to groupware system |
YES (unidirectional) |
|
| Details, Limitations and Restrictions | Synchronization of additional fields ("field mapping" 9 ) | YES |
| Tasks | ||
| synchronization of tasks from Aurea CRM to groupware System |
YES (basically unidirectional) |
|
|
Details, Limitations and Restrictions |
Synchronization of additional fields ("field mapping" 10 ) | YES |
| bi-directional Synchronization of Status | YES | |
| Synchronization of participants | NO | |
| Absences | ||
| Synchronization of absences from Aurea CRM to groupware system |
YES (unidirectional) |
|
| Details, Limitations and Restrictions | Synchronization of additional fields ("field mapping" 11 ) | YES |
General features
| General | |
| trigger synchronization manually | NO, server side, rule-based synchronization |
| server side installation | YES, no client side installation required |
| Filtering list of synchronization users | YES, see CollectedMailboxes.xml and Additional conditions on rep (ID) table. |
| Open synchronized appointments, e-mails and contacts in CRM from Outlook | YES, via link to Aurea CRM web link 12. |
| Inform and stop on error | YES, see Error Handling. |
| Writing performance data to performance counters | YES, see Writing performance data to performance counters. |
Functional scope– details, limitations and restriction
1 From a technical point of view, synchronization of recurring appointments means, that all occurrences of such serial appointments which are within the synchronization time frame are synchronized to the particular other system as single appointments. The series itself can only be changed in the system where the series has been created, but of course singular appointments of the series can be changed in the other system as well. Such changes result in an exception in the originating system. For example: if you generate a recurring appointment happening every Wednesday, 2PM and change the occurrence of 11th of April in Aurea CRM, this will not change the series in Outlook itself, but only this appointment.
2 Only recurring appointments,where the chair is a synchronization user
3 Publishing means that such appointments are synchronized unidirectional from Exchange Server to the CRM system solely. See Synchronize Appointments / Synchronization Interval for further details.
4 E.g. if the appointment's subject is "Meeting to Opportunity: Y1-1-100" it would be possible to parse this information in the style sheets and link the appointment to Y1; or do the linking with an Aurea CRM trigger.
5 Note, that unlike (old) update.seven connector "classic" edition, connector SE doesn't support "marking appointments as 'free'", but solely supports deletion of appointments in Outlook. Activities (MA) are not physically deleted in Aurea CRM, but only marked.
6 It is not only possible to generally activate or de-activate the synchronization of private appointments, but also possible to define the behavior of connector SE on user level. See Handling Private Appointments for further details.
7 Advanced customization allowing for extending the out-of-the-box field mapping - see Synchronization of Additional Outlook Fields for further details.