GETTING STARTED
SearchAssist Overview
SearchAssist Introduction
Onboarding SearchAssist
Build your first App
Glossary
Release Notes
What's new in SearchAssist
Previous Versions

CONCEPTS
Managing Sources
Introduction
Files
Web Pages
FAQs
Structured Data 
Connectors
Introduction to Connectors
Azure Storage Connector
Confluence Cloud Connector
Confluence Server Connector
Custom Connector
DotCMS Connector
Dropbox Connector
Google Drive Connector
Oracle Knowledge Connector
Salesforce Connector
ServiceNow Connector
SharePoint Connector
Zendesk Connector
RACL
Virtual Assistants
Managing Indices
Introduction
Index Fields
Traits
Workbench
Introduction to Workbench
Field Mapping
Entity Extraction
Traits Extraction
Keyword Extraction
Exclude Document
Semantic Meaning
Snippet Extraction
Custom LLM Prompts
Index Settings
Index Languages
Managing Chunks
Chunk Browser
Managing Relevance
Introduction
Weights
Highlighting
Presentable
Synonyms
Stop Words
Search Relevance
Spell Correction
Prefix Search
Custom Configurations
Personalizing Results
Introduction
Answer Snippets
Introduction
Extractive Model
Generative Model
Enabling Both Models
Simulation and Testing
Debugging
Best Practices and Points to Remember
Troubleshooting Answers
Answer Snippets Support Across Content Sources
Result Ranking
Facets
Business Rules
Introduction
Contextual Rules
NLP Rules
Engagement
Small Talk
Bot Actions
Designing Search Experience
Introduction
Search Interface
Result Templates
Testing
Preview and Test
Debug Tool
Running Experiments
Introduction
Experiments
Analyzing Search Performance
Overview
Dashboard
User Engagement
Search Insights
Result Insights
Answer Insights

ADMINISTRATION
General Settings
Credentials
Channels
Team
Collaboration
Integrations
OpenAI Integration
Azure OpenAI Integration
Custom Integration
Billing and Usage
Plan Details
Usage Logs
Order and Invoices
Smart Hibernation

SearchAssist APIs
API Introduction
API List

SearchAssist SDK

HOW TOs
Use Custom Fields to Filter Search Results and Answers
Add Custom Metadata to Ingested Content
Write Painless Scripts
Configure Business Rules for Generative Answers

Field Mapping

The Field Mapping stage in Index Pipeline is used to map fields in an index pipeline document to a target field.

You can:

  • Set a field value, Rename a field, Copy one field to another, and Remove a field.
  • Define a condition for the field mapping stage. The field mapping actions occur on the documents that satisfy the given condition.
  • Re-order or delete a field mapping.
  • Simulate the changes before saving them.

Ensure to Train your app each time you make changes to any index configuration. This builds the index based on the updated configurations.

Configuration

To configure field mapping, follow the below steps:

  1. Click the Indices tab on the top.
  2. On the left pane, under the Index Configuration section, click Workbench.
  3. On the Workbench (Index Configuration) page, on the Stages column, click the + icon.
  4. On the right column, select Field Mapping from the Stage Type drop-down list.
  5. Enter a name in the Stage Name field.
  6. Enter a condition in the Condition field. You can add multiple conditions using AND/OR connectors. Documents that satisfy the condition are executed as part of the stage. See below for details.
  7. Select an action from the Action drop-down list. See below for details.
  8. Click Simulate to verify the configurations. The simulator displays the Source and the number of documents to which the mapping was applied, and the result. You can change the Source (if not mentioned in the condition) and the number of documents.
  9. Once done, click Save Configuration on the top-right.

For example, select Set from the Actions drop-down list; enter Title in the Field Name field and enter Heading in the Value field. Click Simulate to verify if the field value is changed.

Actions

This stage supports actions like Set, Rename, Copy, and Remove. 

  • Set – This allows you to set a Value for the Field Name.
  • Rename – This allows you to set a New Name for the Field Name.
  • Copy – This allows you to copy the Source Field to the Target Field.
  • Remove – This allows you to remove the Field Name.

You can use the handlebar to reorder the action sequence.

Conditions

Condition is of the following format: ctx.fieldtype==value or ctx.fieldtype!=value.

For example, ctx.contentType=="web" to restrict the mapping to content from a web source.

Field Mapping

The Field Mapping stage in Index Pipeline is used to map fields in an index pipeline document to a target field.

You can:

  • Set a field value, Rename a field, Copy one field to another, and Remove a field.
  • Define a condition for the field mapping stage. The field mapping actions occur on the documents that satisfy the given condition.
  • Re-order or delete a field mapping.
  • Simulate the changes before saving them.

Ensure to Train your app each time you make changes to any index configuration. This builds the index based on the updated configurations.

Configuration

To configure field mapping, follow the below steps:

  1. Click the Indices tab on the top.
  2. On the left pane, under the Index Configuration section, click Workbench.
  3. On the Workbench (Index Configuration) page, on the Stages column, click the + icon.
  4. On the right column, select Field Mapping from the Stage Type drop-down list.
  5. Enter a name in the Stage Name field.
  6. Enter a condition in the Condition field. You can add multiple conditions using AND/OR connectors. Documents that satisfy the condition are executed as part of the stage. See below for details.
  7. Select an action from the Action drop-down list. See below for details.
  8. Click Simulate to verify the configurations. The simulator displays the Source and the number of documents to which the mapping was applied, and the result. You can change the Source (if not mentioned in the condition) and the number of documents.
  9. Once done, click Save Configuration on the top-right.

For example, select Set from the Actions drop-down list; enter Title in the Field Name field and enter Heading in the Value field. Click Simulate to verify if the field value is changed.

Actions

This stage supports actions like Set, Rename, Copy, and Remove. 

  • Set – This allows you to set a Value for the Field Name.
  • Rename – This allows you to set a New Name for the Field Name.
  • Copy – This allows you to copy the Source Field to the Target Field.
  • Remove – This allows you to remove the Field Name.

You can use the handlebar to reorder the action sequence.

Conditions

Condition is of the following format: ctx.fieldtype==value or ctx.fieldtype!=value.

For example, ctx.contentType=="web" to restrict the mapping to content from a web source.