# Post-Ingestion Tasks - System Jobs
After you have added an external data source to your Tenant configuration, the Aisera Gen AI platform runs a RAG index on the data and then displays it via the SOR menu items.
Navigate to the SOR menu in your Aisera Admin UI and select one of the sub-menus to see the data from your enterprise application (3rd Party/external) data source.
The ingested data fields are shown in the lower section of the **Tickets**, **Knowledge**, or **Serice Catalog** page. For directions on how to change the mapped fields, see **Field Mapping**.
#### Data Preparation
There are post-ingestion tasks that you may need to complete before your ingested data is ready for use. These include creating data maps for custom fields, and making sure your Knowledge Articles contain the content tags you want to use.
{% hint style="info" %}
**NOTE:** Some of the operations in this section may need advanced Administrative permissions. If you cannot see or perform these commands, see your Aisera onboarding team or Aisera Customer Support.
{% endhint %}
## Running System Jobs
The Aisera Gen AI platform contains many system jobs for internal and external use, including: [**Neural Search**](https://aisera.com/blog/neural-search-enterprise/) **RAG indexing**, **Knowledge Article indexing**, running **Access Attribute Extraction** jobs for **User** data, or running **Discovery Ontology Indexing** for Ticket data.
System Indexing Jobs
The steps for running System Jobs are all the same, but each job may require different parameters. You may need to talk with your data source administrator to gather some of these parameters.
#### To Run a System Job:
1. Navigate to **Settings > System Jobs** in the Asera Admin UI.
2. Select the **Generic Jobs** tab near the top of the window.
3. Select the **+ New Job** button in the upper-right corner of the window.
4. Scroll down the **Select Job** list and choose the job you want to run.
5. Select the **OK** button.
6. If your job requires specific parameters, more configuration windows will appear.
7. Select **OK** after entering the parameters for each window.
8. Select **OK** again on the confirmation window that asks, **Are you sure you want to run this job?**
9. Navigate to **Settings > Jobs** to track the progress of your job.
### Description of Frequently Used System Jobs
| System Job | Description | When to Use | Parameters |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Neural Search RAG Indexer** | Turns knowledge chunks into Vectors - a mathematical representation of the chunks for a more efficient search. **NOTE:** This option requires the **Private KB Fulfillment Type** to be enabled in the **AiseraGPT Advanced Settings** tab. | Whenever any new/updated documents are added to an AiseraGPT (Agent’s) knowledge graph |
Toggle use-synonyms on
(Optional) Toggle enable-incremental-updates
(Optional) Toggle reset-index (only use in rare-cases where you want to completely wipe the existing indices and start fresh).
(optional) Configure data-sources by ID (IDs can be found in the data source configuration page). Only use if you have large volumes of documents (hundreds / thousands) and only want to update specific data source(s) to prevent a long job-run.
Click OK
|
| **Neural Search Flow Indexer** |
Turns the description and use-cases text-bodies attached to Workflows / Hyperflows into chunks, and turns those chunks into Vectors - a mathematical representation of the chunks for a more efficient search. NOTE: This option requires Flow with No Intent (Intentless) Fulfillment Type to be enabled in the AiseraGPT Advanced Settings tab.
| After adding or updating any Workflow/Hyperflow **Description/Use-cases** field. | |
| **Neural Search Service Catalog Indexer** |
Turns the description text-bodies attached to Service Catalog Items into chunks, and turns those chunks into Vectors - a mathematical representation of the chunks for a more efficient search. NOTE: Requires Service Catalog Fulfillment Type to be enabled in the AiseraGPT Advanced Settings tab. Also requires Service Catalog Data Source configured and Service Catalog Knowlege Learning job to be executed in the tenant.
| When you want to make service catalog items conversationally searchable and accessible in the chat via hyperlink. or | |
| **Ontology Generation** |
Used to discover new entities (words / terms / acronyms) / synonyms in client-provided data (Knowledge Docs, Ticket Data) to improve RAG search accuracy. Example: If a bot user asks about "at-home fitness," but your document only uses the term "calisthenics," a basic search might miss it.
| Whenever new data source content is added to an AiseraGPT (Agent). |
Navigate to LLMs -> Ontology -> + New -> Ontology Generation
Provide Any Name
(Optional) Filter for specific data sources (Data Sources shown are only those which have been added to the AsieraGPT Bot in context).
Add some use-cases to give the LLM model an example of the type of content and specific terminology to search.
|
| **Knowledge Learning** | Singular Job to Load, Clean, Chunk, and Embed Knowledge Articles into the Aisera Knowledge Graph. | Upon Creation / Update of Knowledge Learning Data Sources. | Run using the Start button on the Data Source that contains your Knowledge Articles. |
| **Service Catalog Learning** | | When you create or update a Service Catalog. | Run using the Start button on the Service Catalog Data Source. |
### Ontology Jobs
The ontology for your application/bot is added when you choose the **Domain** (HR, IT, Medical) in the first steps of creating your application/bot.
However, you can run a job to enhance the existing ontology or create a new ontology. Follow the steps in the table above, at the right side of the Ontology row. This is not specifically a System Job, but you can track the progress in the **Settings > Jobs** window.
### Learning Jobs
Learning jobs run automatically when your data source connection to the tenant is complete. A separate learning job runs for Tickets, Knowledge Base Articles (Knowledge), and Service Catalog Items (most often used with ServiceNow data). The Aisera Gen AI platform will ingest data from all of the fields that are pre-mapped or manually mapped.
#### To run a Learning Job manually:
1. Navigate to **Settings > Data Source**.
2. Choose the a source that's connected to your Aisera Gen AI platform.
3. Select the **Start (Run)** button at the top of the window.
## Job Sequencing
If you plan to run more than one System Job sequentially, for a new or updated database, use this order:
* Run Knowledge Learning against the KB data source(s) - automatic
* Run Ontology Generation to discover new Entities / Synonyms
* Run Neural Search RAG Indexer to turn new/updated knowledge chunks into searchable vectors.
### More Tasks
In addition, you may want to:
* test your bot with [**AI Lens**](/aisera-platform/ai-workbench-optimize-conversations/ai-lens.md)
* add or modify [**Workflows**](/aisera-platform/ai-automation-optimize-flow/ai-workflow-studio.md) or [**Hyperflows**](/aisera-platform/ai-automation-optimize-flow/hyperflow-studio.md)
* create **Events** with [**Event Studio**](/aisera-platform/ai-automation-optimize-flow/event-studio.md)
* add [**Ontologies**](/aisera-platform/llm-operations/ontology.md) for **Tickets**
* analyze [**Unresolved**](/aisera-platform/ai-workbench-optimize-conversations/analysis-of-unresolved-conversations.md) conversations with AI Workbench, make revisions, and iterate
* research [**Analytics**](/aisera-platform/analytics/analytics.md), make revisions, and iterate
* customize prompts using the [**Prompts Studio**](/aisera-platform/llm-operations/prompts-studio.md)
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.aisera.com/aisera-platform/adding-data-to-your-tenant/post-ingestion-tasks-system-jobs.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.