Additional objects concepts

Glean has the ability to crawl additional native objects which are not crawled by default and custom Salesforce objects, which can be set in the Admin console under the Salesforce data source and object tab. Glean requires the object name, permission model, and mapping of fields for Title and Owner and optional filters.

• If adding a new native object, the integration account configured to use Salesforce must either be a full administrator or be configured with the following permissions (either the Profile or the User under Setup)
  • Object Permissions for the new native object – view all + read access to all fields

Schema

Glean requires the field names of the Salesforce API, which will be utilized to populate document metadata and present it on the Glean user interface. The field name for the Native or Custom Object is found in the Field Name column under Field & Relationships.

Custom objects typically conclude with the suffix __c. Below is an example of Salesforce API field names associated with one of our test custom objects.

Document title

The Field Name will populate the title for the documents seen on Glean under search results.

Document owner

By default, it is the OwnerID.

Custom facets

As an option, provide all the fields that are wanted as a facet (a way to filter a search) and/or as an indexable field

• Indexable fields types:
  • Textarea
  • String
  • Email
  • Picklist
  • multipicklist

Notes:

• All salesforce API fields that are specified as custom properties with type “indexable field types” will be searchable within Glean
• Indexable fields are the ones whose content is searchable on Glean
• Types are inferred from the Salesforce object schema. Each native object has a predefined type, and for each custom object, you specify the type while setting it up
• All the fields (including indexable and non-indexable fields) will be added as a string facet within Glean