The download page is accessible from the application preferences menu. You have an Employee role and a Resource role, and you have either a Sales Representative role, or a Sales Manager role; you must not have both the Sales Representative and Sales Manager roles.
You also must not have a Sales Administrator role. The security certificate ensures the secure exchange of data between Microsoft Outlook and Oracle Fusion CRM during synchronization, and therefore must be installed on every user's laptop or PC. To install the Oracle Fusion CRM for Microsoft Outlook security certificate you must download the security certificate, add the Certificates Snap-In to the Microsoft Management Console, add the security certificate to the personal certificate store, and lastly, add the security certificate to the trusted root certification authorities store.
If you require a different version of the security certificate you must uninstall the original certificate using the Microsoft Management Console. To provide users access to a new client configuration, you can either create a new deployment package or create a new instance of an existing package, as discussed in the following sections.
When you create a new package, in addition to activating it, you must configure a data security policy that allows users to access the package. In the top left section of the APM application window, use global search to search for Database Resources using search criteria equal to Outlook.
This should return the result, Outlook Edition Metadata Package. In the Edit Database Resource tab, select the Condition tab and create a new condition on the database resource. Repeat step 2. Select the lookup control next to the condition field and select the new condition created in step 3.
When you use an existing package, you create a new instance of the package with different configuration files. When using this method, you must inactivate the previous instance and activate the new instance. There is no need to configure a data policy when creating a new instance of an existing deployment package. One of these tasks is to deploy the Fusion Public Certificate to each user's machine in order to support secure exchange of data between Outlook and Oracle Fusion CRM during synchronization.
If users have sufficient privileges and knowledge to import the certificate themselves, they need to make sure the certificate is imported to both the Personal and Trusted Root Authority certificate stores.
This can be done by following these steps:. Select the Add button to add it. Select the option to manage certificates for My user account and select Finish. Select Close and OK to complete adding the Certificate snap-in.
Expand the Certificates - Current User group to review all the certificate stores. In the next several windows, find the certificate file and complete the import into the Personal certificate store.
Repeat step 7 using the Trusted Root Certification Authorities store, and repeat step 8 to import the certificate file. Alternatively, to automate the installation of the public certificate into the appropriate certificate stores on the users' computers, deploy the CertMgr. In the script above, the placeholder for the certificate name would be replaced with the name of the certificate file for example, oracle.
The Outlook application must be closed during this process. During the install, the user will specify:. In this case, the administrator will access the installer file from the appropriate preference page in the Oracle Fusion Sales application and write a batch script to run the installer with several default parameters, such as the install directory, the mail profile to install to, and all of the elements of the connect string.
The name and relative path to the installer file. In the example, the script assumes that the. The one provided in the example above is the default deployment path for the CRM for Microsoft Outlook application, and it will typically be used. Note that the script is using the standard switches provided by the Microsoft Installer executable, msiexec. Documentation of the switches can be reviewed by typing msiexec.
Once the installer finishes, the first time the user opens Outlook there will be additional dialogs that prompt the selection of various application options. This process is called the First Run Assistant, and each user will specify:. Once the user credentials and connect string are provided, the application will connect to Fusion to download and apply the Outlook configuration available to the user.
Once the configuration is applied the user is presented with additional First Run Assistant dialogs to complete the personalization process and perform an initial synchronization. In this second phase of the First Run Assistant, the user will specify:. Synchronization settings, including the default synchronization frequency and synchronization filters.
The application synchronizes data based on synchronization filters, and will automatically initiate a syncronization on the specified frequency. Once the user completes the First Run Assistant, the application will begin the first synchronization. One of these tasks is to verify each user's computer has the necessary supported software prior to installing CRM for Microsoft Outlook.
Profile with a Microsoft Exchange e-mail account configured in cached mode with single mailbox. Outlook needs to be run with this profile at least once. Profile with an Internet e-mail account. Depending on what data file is set as the default mail delivery location in the Outlook profile selected for CRM for Outlook installation, it can be either:.
The IMAP protocol has a unique structure. Whether or not a custom folder can be created in this protocol depends on the mail server. The CRM for Outlook platform requires the ability to add custom folders, and needs to be able to syncronize custom CRM objects for example, accounts or opportunities with Outlook. The IMAP protocol cannot be made the default mail delivery location in Outlook, and the CRM for Outlook platform installs to the default mail delivery location in the profile.
Either Exchange mailbox or POP. A default mail delivery location is required for the platform, as all Outlook activity processing happens there for example, meeting participants receive notification from the organizer only in this location.
Changing the default mail delivery location in the Outlook profile where CRM for Outlook is installed is not supported because doing so will cause the CRM for Outlook add-in to fail.
The application is deployed to Outlook using the add-in framework and extends the Outlook data model and UI framework in order to store and render CRM data to the user. While working in Outlook, users access CRM data that is stored locally, even when connected to the corporate network. There are two options for storing the CRM data:. A Microsoft Outlook mail profile configured to use a Microsoft Exchange service with the Use Cached Exchange Mode enabled to allow data to be stored in an offline storage file.
A Microsoft Outlook mail profile configured to use the Internet E-Mail service with personal folder storage. Because CRM data is maintained in Outlook storage, it can be displayed and accessed like any other Outlook item. After the STS identity provider has been configured, you must have the following:. Export ADFS 2. The certificate Distinguished Name obtained from the signing certificate. The issuer, for example, is in the form login-stage.
Oracle then requests you to confirm if Outlook SSO enablement is required. The new service request is assigned to the support team, who collaborates with Oracle Cloud Operations to complete your cloud service environment setup.
Oracle provides detailed steps to complete the setup. Integrating Active Directory Federation Services 2. You must use the predefined connector. Search for the host name slc01aib. Search for the host name fuscdrmovmcrm-ext. Select App. Browse to select your connector.
If you need assistance with enabling STS for Sales for Outlook, open a service request using these details:. Sales for Outlook uses a configuration file called connector. This topic explains how to obtain the connector. After you complete the installation with the STS authorization mode enabled, the Sales for Outlook - Login dialog box appears, as shown in this figure:.
This topic explains the configuration file structure and provides steps to configure the connector. This section explains the structure of the configuration file and the general settings. A set of endpoint action.
This section specifies which service certificates to use. A set of bindings that describe the method and corresponding properties Sales for Outlook should use to connect to the service. A set of endpoints that contain URLs of services, binding names, and action names. Security token caching settings. Caching only applies to STS configurations. A set of web service configuration profiles. Describes endpoint names to use as well as the readable information that's shown in the Credentials dialog box.
The profiles are displayed in the Credentials dialog box in the same order as declared in the following example. The Profile node structure is the same as shown in the following example, where the text given inside the CDATA [] tag represents the description shown to the user in the Login dialog box:. Unique internal profile name.
This name is used to store the user-selected profile. Select Close and OK to complete adding the Certificate snap-in. Expand the Certificates - Current User group to review all the certificate stores. In the next several windows, find the certificate file and complete the import into the Personal certificate store.
Repeat step 7 using the Trusted Root Certification Authorities store, and repeat step 8 to import the certificate file. Alternatively, to automate the installation of the public certificate into the appropriate certificate stores on the users' computers, deploy the CertMgr.
In the script above, the placeholder for the certificate name would be replaced with the name of the certificate file for example, oracle. The Outlook application must be closed during this process. During the install, the user will specify:. In this case, the administrator will access the installer file from the appropriate preference page in the Oracle Fusion Sales application and write a batch script to run the installer with several default parameters, such as the install directory, the mail profile to install to, and all of the elements of the connect string.
The name and relative path to the installer file. In the example, the script assumes that the. The one provided in the example above is the default deployment path for the CRM for Microsoft Outlook application, and it will typically be used. Note that the script is using the standard switches provided by the Microsoft Installer executable, msiexec. Documentation of the switches can be reviewed by typing msiexec.
Once the installer finishes, the first time the user opens Outlook there will be additional dialogs that prompt the selection of various application options.
This process is called the First Run Assistant, and each user will specify:. Once the user credentials and connect string are provided, the application will connect to Fusion to download and apply the Outlook configuration available to the user.
Once the configuration is applied the user is presented with additional First Run Assistant dialogs to complete the personalization process and perform an initial synchronization. In this second phase of the First Run Assistant, the user will specify:. Synchronization settings, including the default synchronization frequency and synchronization filters.
The application synchronizes data based on synchronization filters, and will automatically initiate a syncronization on the specified frequency. Once the user completes the First Run Assistant, the application will begin the first synchronization.
The application is deployed to Outlook using the add-in framework and extends the Outlook data model and UI framework in order to store and render CRM data to the user. While working in Outlook, users access CRM data that is stored locally, even when connected to the corporate network. There are two options for storing the CRM data:. A Microsoft Outlook mail profile configured to use a Microsoft Exchange service with the Use Cached Exchange Mode enabled to allow data to be stored in an offline storage file.
A Microsoft Outlook mail profile configured to use the Internet E-Mail service with personal folder storage.
Because CRM data is maintained in Outlook storage, it can be displayed and accessed like any other Outlook item. For instance, CRM data types will appear in the folders for the user's mailbox alongside other native Outlook types, and users can select the CRM folder and view the CRM records there as they would work with other Outlook information. Within a given folder, the user can select and open a single record to view the data. In this case, the user will have access to CRM data that appears within an Outlook form or inspector window.
In addition to accessing CRM data in Outlook explorer views and inspector windows where the CRM data is the primary focus, users will also be able to access CRM context when viewing standard Outlook items like appointments, e-mails, and tasks.
For these Outlook types, the user will be able to specify the CRM customer, related sales item, contacts, and resources associated with the Outlook item, and will be able navigate to the related CRM item to review additional details. Data that is stored in either cached Exchange mode in. The user interacts with the CRM data that is stored locally on his computer and periodically synchronizes data between Outlook and the Fusion CRM server.
Synchronization happens when the user is connected to the corporate network and can access the CRM application server. Because the user always works with the local set of CRM data, he will have access to the data from the server immediately following the synchronization process, but doesn't directly access or update the data on the server.
Changes are made to the local data set, and then the synchronization process takes care of making changes to the local or server data sets to align the two. Several synchronization settings are configured as part of the First Run Assistant process that influence the initial synchronization. These include the frequency of automatic synchronization, the synchronization filters to use, and which objects are enabled or disabled from synchronization.
These settings can be changed by the user after the initial synchronization. Once the user completes the First Run Assistant process, the initial synchronization will begin.
The duration of the synchronization process will depend on the number of records that will be synchronized, network bandwidth, load on the server, as well as processing speed and memory available on the user's computer. A rule of thumb is to try to configure synchronization filters so that no more than five to ten thousand records are synchronized. Performs a check to determine the configuration for which the user possesses access. Access to an Outlook configuration is established based on a privilege associated with a user's job role that allows access to an Outlook client deployment package.
If a user has access to a deployment package, it is downloaded, and the configuration is applied to the Outlook mailbox. The final step is to synchronize data.
0コメント