Skip to main content

Content Search Connectors

Content View Connectors or Content Search Connector allow you to search content and then take action against the results. They are used by Content Views in Federation to populate results and update indexes as needed.

Available Content View Connection Types

Elasticsearch Connector

MongoDB GridFS Search Connector

MongoDB Search Connector

SOLR Search Connector (End of Life)

Basic Configuration

Connector Ids

Connector ids are how simflofy identifies the individual connector when receiving calls from other sources, such as Federation Service. This value must be usable as part of url. Use the description field if you need more than a few letters/numbers to describe the connection. The description shows up with its connectorId across the product.

  • Connector ID: A unique identifier for this connection i.e. simflofy_demo (Alphanumeric, dashes and underscore characters only)
  • Description: The text that will be displayed on drop-downs etc. to identify this connection.
  • Type: The type of Search Connection (Solr, Mongo, Elastic etc.)
  • Keep Connection Alive: Simflofy will cache the connection for a given amount of time before discarding it.
  • Keep Alive in Milliseconds: How long to keep the connection alive before discarding it (300000 is 5 minutes)
  • Security Mode: This is how to authenticate with the back-end search.
    • Authentication Connection: The most common method is to use the appropriate authentication connection
    • User Passthrough Credentials: Users the authenticates with whatever authentication they used for Simflofy. Only supported in rare cases.

Result Links are under the Search Configuration tab, but work universally.

If Download is selected, the file names in your view will call a document download, much like the Widget

If External is selected, you will need to add Result Links. When you click the Result Links button a modal should appear. It takes three arguments

  • Content Service Connector: External link configurations are grouped by content service connector.
    • This allows documents from different repositories to form different links
  • Link Field: The document field that contains relevant information for building the link.
  • Link Url: The content of the link field will be appended to this url to create the link.
Link Fields with Semicolons

Due to how certain ids with versions are handled. The value of the link field will be cut off after the first instance of a semicolon(;)

Search Configuration

Refer to the documentation for each connector to see which fields are available.

Search Security

  • Filter:
    The authenticated user's group ids and login will be added to each search request. Requires content to be indexed using the Index User Group TaskSee this example
  • Restrict:
    Only users from the selected groups will be able to use this search connection, regardless of role. If this connection in used as part of a Content View, users outside these groups will not be able to see it in their View List in TSearch.

Connection Configuration

Individuals connectors might have specific fields here that were not general enough to be in Search Configuration

Additionally, this is where you can use the "Add Custom Parameter" button to set any default query values for the connection.

A query_fq configuration param lets you define facet queries behind the scene. This is done to provide limited views or subsets of data in the search. Essentially you could create any number of views on the same date but each view would display different results. This can also be used in a role base system where you have views setup for specific user roles.Unless the fq is already encoded, you will need to wrap it in the encode() function where it will be URLEncoded UTF-8.

The syntax is:

query_fq for the first one

query_fq1 for the second


Related Articles:
Using Simflofy Federation
TSearch Dashboard Widget Tutorial
Content Search REST Endpoints