Appearance
Glossary
| Term | Definition |
|---|---|
| Any Schema | A built-in catch-all schema that accepts any fields; not recommended for data feeds |
| API Client | Credentials for external systems to authenticate when calling HTTP API connectors |
| Batch Size | The number of datapoints processed in a single workflow step run |
| Bucket | A logical container that groups related datapoints together |
| Chaining | Connecting workflow steps together so data flows through multiple processing steps |
| Capability | An automatically detected feature of a connector operation, shown as a badge in the UI (e.g., Paging, Checkpoint resume) |
| Checkpoint | The last successfully processed position, enabling the system to resume without duplication or data loss |
| Child Customer | A sub-organization managed by a vendor account |
| Compute Specification | Resource allocation (CPU/memory) for out-of-process workflow step execution |
| Connector | A reusable integration component that bridges external systems with YuzeData |
| Connector Instance | A deployed connector with specific configuration and credentials |
| Connector Template | A blueprint defining connector settings and available operations |
| Consume | Input data for a workflow node |
| Customer | An organization account in YuzeData |
| Data Feed | A mechanism for workflows to produce and consume datapoints between each other |
| Data Feed Trigger | A trigger that runs a workflow step when new datapoints arrive in a consumed feed |
| Datapoint | An immutable data record representing an event or measurement, created during workflow execution |
| Direct Mode | Connector invocation mode where workflows invoke connector operations on demand |
| Event Subscription | A configuration that forwards system events to external services via webhooks |
| Export Master Data | A workflow step template that pushes master data from YuzeData to an external system |
| Expression | A YuzeScript code block in schema mappings that calculates or transforms field values |
| External Identifier | A reference to a master data item using an external system's ID (format: master-data-ext:{type}:{source}:{key}) |
| Group | A collection of users that share the same roles and permissions |
| HTTP API Connector | A connector that exposes an HTTP endpoint for external systems to send or retrieve data |
| HTTP API Mode | Connector invocation mode that exposes an inbound HTTP endpoint for external systems |
| Identity Provider (IdP) | A service that authenticates users (e.g., Azure AD, Okta) |
| Import Master Data | A workflow step template that pulls master data from an external system into YuzeData |
| Incremental Sync | Syncing only items that changed since the last sync, reducing load on external systems |
| In-Process | Workflow step execution mode that runs within standard processing infrastructure |
| Internal Identifier | A reference to a master data item using its YuzeData key (format: master-data:{type}:{key}) |
| Key Field | A schema field whose value forms part of a master data item's unique identifier |
| Map Field | A schema mapping task that copies data from a source field to a target field |
| Mapping Identifier | A link between a master data item and its ID in an external system |
| Mapping Task | A step in a schema mapping that defines how a field is transformed |
| Master Data | Mutable reference data representing real-world entities that can be updated over time |
| Master Data Type | A category of master data items (e.g., Equipment, Location, Supplier) |
| Node | A single step in a workflow |
| Notification | An automated message sent to users on a schedule (reports, alerts) |
| OAuth2 | An authentication protocol used by API clients for secure access |
| Operation | A discrete action a connector can perform against an external system. Operations display capability badges indicating their advanced features |
| Out-of-Process | Workflow step execution mode that runs in a dedicated container with configurable resources |
| Parent Workflow Step Trigger | A trigger that runs a workflow step after another workflow step completes |
| Permission | An authorization that allows access to specific features or actions |
| Position | An auto-incrementing number assigned to each datapoint, establishing order |
| Position Tracking | Using checkpoint positions to ensure exactly-once processing of datapoints |
| Produce | Output data from a workflow node |
| Provide Value | A schema mapping task that injects a constant value into a target field |
| Reference Data Item (RDI) | See Master Data |
| Role | A named set of permissions that can be assigned to users or groups |
| Schedule Trigger | A trigger that runs a workflow step at specified time intervals |
| Schema | A definition of data structure (fields and types) |
| Schema Mapping | A transformation that converts data from one schema to another |
| Secret Setting | A connector setting containing sensitive data (API keys, passwords) that is encrypted and never displayed |
| SSO (Single Sign-On) | Authentication using an external identity provider |
| Sync Status | Tracks which master data items have been synced and their versions |
| Trigger | A mechanism that starts a workflow step (schedule, data feed, or parent workflow step) |
| User | An individual account that can access YuzeData |
| Vendor | A customer account type that can manage child customers |
| Webhook | An HTTP callback that sends data to external systems when events occur |
| Webhook Signature | An authentication method where requests are signed with a shared secret |
| Workflow | A data integration process that orchestrates the flow of data between systems |
| workflow step | A reusable step within a workflow that performs a specific operation |
| workflow step instance | A configured step in a workflow, created from a workflow step template with specific settings |
| workflow step template | A blueprint defining a type of workflow step operation |
| YuzeScript | YuzeData's JavaScript-based scripting language for custom logic and data transformations |
