Glossary
This glossary defines the core terms used across Adeptia platform documentation, covering integration objects, data management concepts, and knowledge base categories.
Integration objects
| Term | Definition |
|---|---|
| Workflow | An integration process managed and executed on the Adeptia platform. |
| Transaction | An integration entity tracked and listed within the platform. |
| Source | A configured entry point from which the platform reads incoming data. Sources define the protocol and location from which data is retrieved. |
| Layout (Schema) | A structural definition that describes the fields, hierarchy, and format of a data payload. Layouts are used on both the source and target sides of a mapping. |
| Mapping | A transformation definition that specifies how fields from one or more source layouts are converted and written to a target layout. |
Data enrichment and crosswalk objects
| Term | Definition |
|---|---|
| Value Map | A crosswalk table that translates a single source field value to a corresponding target value. Value maps can be scoped globally or to a specific project. |
| Multi-valued Map | A crosswalk table that translates a single source key to multiple output column values simultaneously. Like value maps, multi-valued maps support global and project scopes. |
| Enrichment Source | A registered external data source (such as a database, API, CSV file, or value map) that the platform can query at runtime to add supplementary fields to a record. |
| Use-case Template | A reusable configuration pattern that captures the structure of a common integration scenario, allowing non-engineers to apply or update it without code changes. |
Mapping concepts
| Term | Definition |
|---|---|
| IR (Intermediate Representation) | A full-fidelity, lossless representation of a mapping's working state. Storing the IR allows a mapping to be reopened and edited exactly as it was last saved. |
| XSL | The stylesheet format that the platform compiles a mapping into for execution. XSL is the runtime form of a mapping definition. |
| Mapping rule types | The categories of transformation logic that can be applied to a field in a mapping: direct field copy, transform expression, constant value, and concatenation. |
| Value map reference | A mapping rule that routes a source field through a named value map crosswalk to produce the target value, rather than copying or computing it directly. |
| Join hint | A result returned by the join-detection capability indicating a potential relationship between source datasets. |
| Preflight check | A dry-run validation that reports which mapping rules the platform would drop during deployment, without actually deploying the mapping. |
Execution and monitoring concepts
| Term | Definition |
|---|---|
| Execution | A single run of a workflow or process flow, capturing its status, timing, and step-level results. |
| Execution history | The record of past executions for a workflow, filterable by status, transaction, and partner. |
| Audit log | An activity-by-activity trail for a specific execution, recording each step taken during the run. |
| Context info | The set of runtime variables and parameters that were active during a specific execution. |
| Automation overview | A dashboard view that summarizes execution trends, completed and pending runs, transaction types, and process flow activity across the tenant. |
| Trigger dashboard | A monitoring view that shows event chart data, triggered processes, active triggers, and any process or trigger errors. |
Knowledge base concepts
| Term | Definition |
|---|---|
| Collection | A named, tenant-scoped container in the knowledge base that holds indexed documents. Each collection belongs to a single organization. |
| Document | A file ingested into the knowledge base and broken into searchable chunks. Supported document types include PDF, DOCX, TXT, HTML, and others. |
| Taxonomy path | A hierarchical label applied to a document at ingestion time that places it within a category tree, making it easier to browse and filter. |
| Semantic search | A retrieval method that matches a natural-language query to relevant document chunks. |
| Ingestion job | An asynchronous task created when a document is submitted for indexing via the async ingestion path. The job can be monitored by its identifier until it reaches a completed or failed state. |
| Preferences | Stored customer-specific settings associated with a knowledge base collection that guide how the platform interprets or responds to queries for that collection. |
| Rules | Stored customer-specific directives associated with a knowledge base collection that constrain or shape the platform's behavior when answering queries. |
Knowledge base categories
Documents ingested into the knowledge base are organized under the following top-level categories.
| Category | Description |
|---|---|
| Terminology / Definitions | Glossaries, term definitions, and concept explanations. |
| Integrations | Documentation covering integration patterns, connector behavior, and end-to-end flow design. |
| Data Mapping | Mapping specifications, field-level transformation rules, and crosswalk references. |
| Schemas and Data Models | Layout definitions, data model diagrams, and schema documentation. |
| Industry and Standards | Industry-standard formats, compliance references, and regulatory guidance. |
| Transformation Rules | Business and technical rules that govern how data is converted or enriched during processing. |
| Architecture and Design | System design documents, architectural diagrams, and platform topology references. |
| Messaging and Eventing | Documentation for event-driven patterns, message queues, and trigger configurations. |
| Logs and Monitoring | Operational runbooks, log interpretation guides, and monitoring dashboards. |
| How-To Guides and Tutorials | Step-by-step instructions for common tasks and platform features. |
| Troubleshooting and Runbooks | Diagnostic procedures, error resolution guides, and operational runbooks. |
| KB Process / Knowledge Doer | Internal knowledge base process documentation and contributor guidelines. |
Tool behavior classifications
Every platform action is classified by the type of change it makes, which determines how the platform warns you before proceeding.
| Behavior | Meaning |
|---|---|
| Read | Retrieves or computes information without changing any platform state. |
| Write | Creates new objects or submits new data, such as deploying a new mapping or ingesting a document. |
| Destructive | Overwrites or removes existing platform state. |
Readiness tiers
| Tier | Meaning |
|---|