Tengence Search User Guide: Build Search into Your App in 4 Steps
This guide walks you through adding search capabilities to your business system with Tengence Search: create an app, configure an index, build the index, and integrate via API or UI component.
What Is Tengence Search?
Tengence Search is a fully managed search product from Tengence that lets enterprises add high-quality search to their applications in minutes—no search infrastructure to deploy or maintain.
The four-step flow:
| Step | Description |
|---|---|
| Create an app | Pick your industry and plan to provision search resources |
| Configure the index | Map dataset fields to index fields and define the search schema |
| Build the index | The system builds the search index automatically based on your config |
| Integrate | Embed search via REST API or a ready-made UI component |
Getting Started
-
Log in to the Tengence Console and click Tengence Search in the left sidebar.
-
You land on the overview page. Click New App to start creating your first search application.
Creating an App
Step 1: Choose Industry and Plan
Select your business industry. The system applies industry-specific tuning automatically. If your industry isn't listed, choose General.
Choose a plan tier. Each tier comes with different resource quotas and features—pick one that matches your data volume.
-
Click Create to finish.
Step 2: Open the App Detail Page
-
After creation, click Back to App List.
-
Your new app appears at the top of the list (newest first). New apps get an auto-generated name.
Click the app name to open its detail page.
Step 3: Understand the "Basic Info" Panel
The app detail page has three main sections: Basic Info, Index Config, and Preview. The Basic Info panel gives you:
| # | Feature | Description |
|---|---|---|
| 1 | Rename | Click the edit icon next to the app name |
| 2 | Actions | Upgrade, renew, or delete the app |
| 3 | Service status | Current plan tier and service state |
| 4 | Runtime status | Shows whether the index is ready; you must complete index config before use |
| 5 | Quota usage | Documents indexed / plan limit; upgrade to raise the cap |
| 6 | Preview | Opens a side panel to see the search UI in action |
| 7 | API access | Shows API endpoint, auth key, and request examples |
| 8 | UI component | Shows the embedded search widget integration guide |
| 9 | Debug console | Test queries and verify your config is working |

Figure 6: The Basic Info panel
⚠️ Important: The API Key authenticates all calls to your app. Keep it secure and never expose it client-side.
Index Configuration
An index is the foundation of search. You map dataset fields to index fields, and the system builds a searchable index from that mapping.
Step 1: Enter Index Config
From the app detail page, click Index Config.
- No dataset yet? Click Create New Dataset to start fresh.
- Already have one? Click Link Existing Dataset and pick from your list.

Figure 7: Index config entry point
Step 2: Pick Your Dataset
Select the dataset that will serve as the data source for this index.
Step 3: Configure Index Fields
Tengence Search provides index templates for common use cases. Start from a template and adjust as needed:
Semantic labels: Tag each field with a semantic label so the system understands your business data better.
Index fields: Templates pre-populate field names. Just map them to your dataset fields. Every index must have exactly one ID field (unique document identifier) and at least one field with tokenized field type for search to work.
Dataset field: Pick which dataset column maps to each index field.
Field type: Choose how each field is processed into the index (tokenized, exact, numeric, etc.).
Field weight: Set a weight for tokenized fields—search results are boosted by weight at query time.
Add custom fields: Click Add Index Field to extend the template with business-specific fields.
Click Save to persist your config.

Figure 9: Index field configuration
💡 Tip: Hover over the "?" icon next to any column header to see a detailed explanation of that setting.
Step 4: Start the Index Build
After saving, a dialog asks whether to start building now. Click Start to kick off the build, or Not now to keep editing.

Figure 10: Starting the index build
Step 5: Track Build Progress
Back on the app detail page, the Runtime status card shows build progress and lets you stop the build if needed.
The Document count shows how many records have been indexed so far.
Click refresh to see the number update in real time.

Figure 11: Monitoring index build progress
Integrating Search
Once the index is built, you can connect search to your product. Tengence Search offers multiple integration paths.
Preview
Click Preview to see how the search UI component looks before you ship it.
API Access
Click API Access to see the full integration guide: endpoint URL, request parameters, and response examples.

Figure 13: API integration guide
UI Component
Click UI Component to get the embed code for a ready-made search box. Drop it into your page and you're done.

Figure 14: UI component integration
Debug Console
Click Debug Console to run test queries directly in the console and verify your index is returning the right results.
Glossary
| Term | Definition |
|---|---|
| App | A search service unit in Tengence Search. Each app has its own index config, API key, and quota. |
| ID field | The unique identifier field in an index. Exactly one per index. |
| Index | The searchable data structure built from your dataset field mappings. |
| Semantic label | A tag describing a field's business meaning, helping the system understand and rank better. |
| Tokenized | A field type that splits text into tokens so users can match by keywords. |
| Field weight | A boost value for tokenized fields; higher weight ranks higher in results. |
| Dataset | A data storage unit in Tengence Data Center. Supports push API, MySQL sync, and behavioral data ingestion. |








Top comments (0)