Goal of this blog:
The goal of this blog is to explain the administration and usage of the client side outlook integration. It should not replace the official documentation which can be found here:
Please check the following link for the latest specifications- choose the latest release.
In addition to the official documentation the blog explains some features and functions more in detail and brings them into a context. Also it should help to understand some functions better from a business point of view and also the current limitations. In some cases which are important to know the blog refers to the right chapter of the official documentation instead of copy and paste the data to the blog
1. General set up – Administrator
All administration work is done from the admin view of the client side server integration within C4C.
Prerequisites for the usage of the client side server integration can be found here:
Please check the following link for the latest specifications – choose the latest release.
1.1. First steps as an administrator
As an administrator you have to do the following steps before you can start to provisioning the new feature to the business users.
Assign the workcenter Email integration to your user role within the standard user administration along with its two views.
The view ‘Groupware settings’ will give you access to the admin features.
The view ‘User settings’ will give you the features which you need as a business user.
As a result you will see a new workcenter ‘Email integration’ with the two views.
Since you are an admin your user will automatically provisioned for the server side outlook integration.
Check the pre-delivered settings and adopt them if required.
In order to do this, a general understanding on how to provision users is required and will be explained now…
The user provisioning is done as follows:
Grant users access to the email workcenter
- Assign the Workcenter ‘Email Integration’ and ONLY the view ‘user settings’ via the standard user administration.
Provision users within the admin view ‘Groupware settings’
- choose the users you want to provision from the list of all C4C users. Then you assign them to an Organization (will be explained later in detail). The Organization determines the Mailbox access type which is used by this group of users (for example Microsoft exchange or Google mail). Based on the settings of the selected Organization a Profile is defaulted (the Profile determines the allowed features and functions within the outlook integration – details will be explained later). The Profile can be changed if required.
As a result each user is assigned to an Organization and has an assigned profile.
Having these two simple steps in mind it is now important to understand more in detail:
- What is an organization
- What is a profile
- How are these entities are connected
The Organization has nothing to do with the Organizational model in C4C. It is just a grouping which allows you to provision multiple users easily. By assigning users to the Organization, the users inherit the configuration for this Organization.
The Organization specifies the Profile which will be inherited by the assigned users and the Mailbox access type.
If you want to integrate C4C with an Microsoft Exchange server choose ‘Microsoft exchange direct logon’
If you want to integrate with Google mail choose ‘Google direct logon’
Microsoft Exchange Impersonation is also supported. Here – if an C4C admin has the rights to fully access the users mailboxes (acting on their behalf) on the exchange server- the admin could specify his user and password for each provisioned user in C4C. As a result, the users do not have to give their credentials.
You need at least 1 Organization for each Mailbox access Type you want to integrate with.
The Profile determines the set of features and functions which is available for a single user / Group of users
It is divided in 2 parts – synch settings and add in settings.
In the synch settings you specify:
- Which C4C Objects are subject to the integration and to what extend
- The look and feel of the Outlook add in for the user with regards to these objects
- General Synch settings
The settings are in the most cases self-explaining and will not be discussed in detail in this document but there are some points which are good to know:
- Currently no custom filters can be applied.
- Limit for objects which are synched is 10.000. the creation date is considered.
- In the ‘Remind about…’ setting you specify the default which is applied to the corresponding object in Outlook. This is done here since the C4C object does not have this function – but it is an important feature in outlook.
- The allowed file extensions you specify for attachments must also be allowed in C4C (finetuning activity)
- The attachment size can not be configured – if you need an adjustment you can raise a ticket to SAP and it will be adjusted by SAP for your tenant.
- Enable auto sharing for email – be careful with this setting. Once flagged every email which has a corresponding contact in C4C is synched with C4C automatically. This might not make sense for many customers and lead to unnecessary email data in C4C. Emails coming from blacklisted domains are not synched automatically.
In the ‘add in settings’ you specify:
- The basic view of the add in which always show 4 fields of your choice:
- The detailed view of the add in:
The detailed view supports editing of fields and mandatory fields.
Fields which are defined as mandatory in your corresponding C4C object should be defined as mandatory also in the add in.
Extension fields are also supported.
make sure to activate the new field for right odataservice C4CODATA under ‘further usage’ when creating the extension field or if the field is created via PDI- the field needs to be included via PDI
1.1.3. Relationship: Organization- Profile
The default profile which is assigned to an organization is just a proposal in order to streamline the user provisioning. You can change the assigned profile during the user provisioning for multiple users or also later for a single user.
1.1.4. Number of Organization & Profiles
Having understood the overall concept- you can now decide how many organizations and different profiles you need for your implementation.
You need at least one organization and profile- these are predelivered.
1.1.5. Check overall settings
Decide to which party role your visits should be synched.
Fill in your administrator email address if you want to receive emails sent by the system as a copy.
For the Gmail integration options check the separate block for Gmail integration and server side add in.
1.2. Managing users
Once you have checked the default settings or created new profiles you can start to provision users from the list of users in the provisioning tab.
As soon as a user is provisioned (and has the corresponding workcenter view assigned) he can start with his initial logon. The users are informed via email about the provisioning if chosen by the administrator during provisioning.
As an administrator you can administrate every single user via the different features you can access in the tab ‘users’.
You will find a description of the possible actions here:
(make sure you select the latest release for the doku)
2. General setup – User
2.1. First steps for a user (mandatory)
Once a user is provisioned by the administrator, he will receive a welcome email (optional) in order to start the initial setup and synch.
The user will have a new workcenter view ‘User settings’ In release 1802 this view is visible in the workcenter pane.
If a user was not provisioned- he will get the following error once he opens the view ‚ user settings‘:
As first step the user has to specify his credentials- therefore he has to open the ‘ change settings’ dialog.
Here he would specify the mail client he wants to use for the integration.
Then- depending on his choice the exchange password needs to be provided. C4C then automatically connects to the exchange server via the standard EWS interface of the Microsoft exchange.
For outlook 365 you get a different initial log on dialog
For using google mail- please check the article about google mail.
2.2. Optional Steps
A user could change the assigned profile according to his preferences himself.
He can either choose an existing other profile or customize an individual one.
A user can change the appearance of the add in and what fields are shown or not- Here the user is restricted by the admin settings for the assigned profile. if an admin has set fields/objects to read only- this can not be changed and a user can not switch from read only to edit .
To learn more about the localization option, please check the official doku:
-> Make sure you choose the latest release.
3. End user features and function
When using the C4C server side integration it is important to understand and differentiate the following 2 cases:
- Work in outlook itself and synch data with C4C
- Working directly with the add in and synch data with C4C
3.1. Working in outlook
Currently the following Objects are supported:
Masterdata: Contacts, Accounts, Individual customers
Transactional data: Appointments, Tasks
The supported objects are limited by the available objects in outlook.
You can create these objects as entities in outlook and also change them.
Masterdata is (depending on your configuration in C4C) always synched with C4C.
Transactional data is synched only if marked as relevant for C4C via outlook categories.
If you create an appointment or task, you can categorize it as relevant for C4C and as a result it is replicated to C4C via an asynchronous web service call.
The synch is triggered automatically every 30 minutes by a background job. The synch interval cannot be configured.
However, in many cases you want to assign your appointment or task to a related object in C4C like an account or opportunity etc.
This can easily be done using the add in -> see next section 3.3.2.
3.2. Working with the add in
The add in is basically a ‘minimized UI for C4C’ whenever you do something in the add in it is just like if you would work in C4C itself. There is no synching of data from outlook to C4C in this case since the data is directly read from/stored in C4C.
However- data created/changed via the add in will be replicated back to outlook in case the changed/created object has already a representation in outlook or is eligible to be synched to outlook.
You have synched your C4C contacts to your outlook. A contact you change via the add in in C4C will update the contact in outlook during the next synchronization.
If you create an appointment via the add in in C4C, the appointment is replicated to your outlook calendar with the next synchronization.
3.3. Features and functions
Most of the features are self-explaining and will not be discussed here – however few things are good to know.
If you click the add in icon, the add in retrieves all contextual data with regards to the selected email. If you enter something in the search field of the add in, the search is not done against the data shown in the add in, but it searches for related objects to your search in C4C. The filter can be applied on the search result. The filter does not apply on the contextual data derived in the add in based on the selected email.
Only 5 items are retrieved for each object found. In Realease 1802 the search takes the first 5 objects based on the alphabetical order of the name. So it makes sense to specify the search term as close as possible. From 1805 on it is planned that the search will return the last 5 objects based on the creation date.
3.3.2. Creating appointments
The 2 typical scenarios when working with appointments and integrated with C4C are:
- User creates an appointment himself
- User receives an appointment
In both cases users most likely do not just want to replicate the plain appointment to C4C but link it to a related object like an account or opportunity etc.
Case a can be achieved easily by leveraging the following feature of the add in:
Option 1: Trigger synch via categorization (no direct assignment to an object possible)
Here you create the appointment in outlook, invite attendees, categorize as C4C relevant.
As a result, the appointment is synched to C4C. If the contact is assigned to an account, the account is derived automatically and assigned to the appointment. If contacts within an appointment are belonging to different accounts, the account is derived from the first contact in the meeting request. If a contact does not belong to any account or is not in C4C- no account is determined- choose option 2 then to have an account assigned.
If an account is determined and the appointment has no description in outlook- C4C adds ‘Appointment <account name>’ as description in C4C
Option 2: Trigger synch via add in (direct assignment to an object possible)
create the appointment in outlook, open add in within the appointment, choose the object you want the appointment to be assigned to within the add in and save it to that object.
The add in will change the ‘save’ button
Now you can save your appointment in outlook.
As a result, you have an appointment in outlook and an appointment saved to C4C.
With the next synch cycle the appointment is synched from C4C to outlook and the color code is updated so you can see that the appointment is C4C relevant.
Whenever you change the appointment in outlook , C4C it is updated and vice versa.
Case b is currently not supported. The server side integration does only allow the synchronization of appointments if you are the organizer.
Good to know:
Appointments which are flagged as ‘Private’ are not synched to C4C.
3.3.3. Creating tasks
The client side outlook integration will create a new subfolder ‘SAP Hybris Tasks’ in your outlook task folder.
Tasks created in C4C
All tasks created in C4C where you are the processor will be synched to this folder.
Tasks where you are the owner, but not the processor will not be synched- they will appear in the outlook of the processor if he is using the client side integration.
Tasks created in outlook
All tasks you create in outlook, regardless of the folder you create them in will be synched to C4C if categorized as C4C relevant.
After the synch to C4C these tasks are moved to the SAP Hybris Tasks ‘ folder.
The fact that you can assign the task in outlook to another outlook user via the button ‘assign task ’will not be considered for the replication to C4C- In C4C the creator of the task in outlook ( visible as ‘from’ in the outlook task) will become the processor AND owner in C4C.
Assigning other processors to tasks which are created in outlook is not supported for the synching to C4C.
3.3.4. Contact Management
22.214.171.124. Manage existing contacts.
The server side outlook integration allows you to manage/work with your contacts which are assigned to you in C4C.
Therefore, you can replicate your C4C contacts to your outlook and they will appear in a separate folder in ‘my contacts’
The folder is created automatically once your user is set up for the integration.
Depending on the configuration for your user
- either all contacts which appear in the ‘my contacts’ query in C4C
- or all contacts which appear under the ‘my teams contacts’ query in C4C
will be synched to your outlook.
Whenever a contact is changed in C4C, the changed data is replicated to outlook and vice versa.
Restrictions to be considered:
- Changing data in outlook could lead to synch errors if the data entered in outlook is not compatible with you C4C configuration.
- The outlook contact object is not aligned with the C4C contact Object. Therefore, the outlook contact cannot consume/display all C4C data and vice versa.
126.96.36.199. Create new C4C relevant contacts in outlook.
All new contacts created in C4C which appear in your ‘my contacts’ / ‘my teams contacts’ query are automatically replicated to outlook.
All new contacts created in the ‘SAP Hybris contacts’ folder in outlook are replicated to C4C. However, outlook might not give the option to maintain all relevant data with a good usability. For example – in most cases a contact must be assigned to an account- outlook does only provide a text field with no reference/value help to C4C. If you specify the account in this text field, C4C will try to derive a corresponding account if possible- but this might lead to errors.
Best practice to create C4C relevant contacts from outlook is using the add in.
The server side integration assumes that a user always works in a certain context to an outlook object. In this case the context can be an email which you have received and you want to create the sender of the email as a new contact in C4C.
The add in will show you that the sender was not found in C4C (based on the sender email address). If you decide to add the contact to C4C, push the contact button and maintain the additional data which is required for the contact- like the account….address, phone etc…
…and save it to C4C.
As a result you will find the contact in C4C.
When selecting an account in the add in- the add in shows all accounts which you are allowed to see according to your authorizations in C4C. Therefore if you choose an account which is not shown in ‘my accounts’ / ‘my teams accounts’ – the contact will be created in C4C, but not replicated to outlook.