Mindbreeze GmbH, A-4020 Linz, .
All rights reserved. All hardware and software names used are registered trade names and/or registered trademarks of the respective manufacturers.
These documents are highly confidential. No rights to our software or our professional services, or results of our professional services, or other protected rights can be based on the handing over and presentation of these documents.
Distribution, publication or duplication is not permitted.
The term ‘user‘ is used in a gender-neutral sense throughout the document.
Before installing the Salesforce connector, make sure that Mindbreeze Server is installed. To install or update the connector, please use the Mindbreeze Management Center.
To install the plug-in, open the Mindbreeze Management Center. Select “Configuration” from the menu pane on the left-hand side. Then navigate to the “Plugins” tab. Under “Plugin Management”, select the appropriate zip file and upload it by clicking “Upload.” This automatically installs or updates the connector, as the case may be. In the process, the Mindbreeze services are restarted.
Click on the “Indices” tab and then on the “Add index” symbol to create a new index.
Enter the index path. Adapt the Display Name of the Index Service and the related Filter Service if necessary
In the "Data Sources" tab, select the category "Salesforce" and, if necessary, a Caching Principal Resolution Service. With the button "Add Data Source" further instances can be added and configured.
The Salesforce instance which should be indexed.
Custom Endpoint URL
The URL of the Salesforce Instance which should be indexed.
The TLS Version which should be used.
Auto is recommended.
The Username of an User with read-only Permissions.
The Password for the Crawling User.
In order to authorize search results, either a Caching Principal Resolution Service or the Authorization Provider is required. In case of a Caching Principal Resolution Service, the following settings can be skipped. The Authorization Provider in the tab “User Email Resolution” needs to obtain search user principals which are Object Type Permissions in Salesforce associated with that user (identified by email address) in ObjectPermissions. Therefore it is necessary to obtain the search user’s email address first if it is not provided by client service.
Disables the resolution of the Username using LDAP.
The email of the searching user.
If "Disable User Email Resolution" isn’t selected, the Username can also be specified.
The domain over which the Username should be resolved.
The password to register to the domain.
After authenication in client service if the username is not the email address than it is necessary to resolve email through LDAP. The required credentials can be provided directly in “Username”, “Domain” and “Password” fields. Alternatively its possible that Kerberos is used for authentication. In this case only “Domain” field should be configured. If domain field is also empty than the first configured domain in Network settings will be used.
In order to obtain the search user’s object type permissions the configured crawler user (see Connection Settings above) should have the “View Setup and Configuration” permissions in Salesforce.
Per default the connector provide a list of object types “Default Object Types” which will be indexed when the crawler is started. For crawling other object types the query in “SOQL Query” field will be used. This query must contain the key column name, display date column name and title column name.
E.g. with the following SOQL query the documents of the type Idea are indexed with the Body metadatum.
SELECT Id, SystemModstamp, Title, Body FROM Idea
By customizing the descirptors one can select individual properties of the tables.The connector detects the fields by iterating the describeSObject Metadata in the Salesforce API.
In addition to the preset "Default Object Types", the parameter "FeedItem" can be specified to index the chatter posts. However, this possibility requires a configuration of a "Salesforce Caching Principal Resolution Service".
All Object types except “Document” and “ContentDocument” that contain a HTML field are crawled with the content of that HTML field as the document content. If there is more than one HTML field, then the field to be used as document content can be configured using “HTML Content Metadata” property, where “Object Type” and “HTML Content Field Name” should be provided. For “Document” objects the content of the “Body” field is crawled as document content. For “ContentDocument” objects the content of corresponding the latest “CurrentVersion” object is crawled as document content.
Select “Advanced Settings” to configure the following settings.
Enable the option “Enforce ACL Evaluation.”
Scroll down and add a new service in the "Services" section by clicking on "Add Service".
Select "Salesforce Principal Resolution Service" and assign a display name.
If a resolution of the user name is desired, this can be implemented via a "Parent Service".