Terminology & Key Concept

Created by Reachware Support, Modified on Sat, 7 Mar at 2:47 PM by Reachware Support

This reference guide defines the core concepts used throughout the Reachware Studio Knowledge Base.

Term	Definition
iPaaS	Integration Platform as a Service — a cloud-based platform that connects different applications and data sources, enabling automated workflows and data synchronization across systems.
System	An application or platform that acts as a source or target for integration, configured with endpoints, authentication, headers, and connection settings to enable data exchange.
Operation	A specific API endpoint or resource in a system performing a specific function (e.g., Create, Update, Delete).
Connection	A secure configuration layer that stores client credentials and access information. The connection defines variables associated with the system, tests API authorization, and validates HTTP requests for the client API.
Flow Templates	Automated workflows that execute a series of steps to integrate data across multiple systems, apply business logic, and transform data formats. Each flow is initiated by a trigger that starts the workflow.
Steps	Individual components that define the core logic of a flow. Steps can include actions, conditions, data transformation, API calls, and other processing operations.
Variables	Dynamic values assigned to defined variables within the System or Operation, allowing for flexible and reusable configuration across different executions.
Mapping	The process of matching fields between different systems within a flow to ensure accurate and consistent data transfer across platforms.
Handlers	Pre-built transformation tools that work like ready-to-use functions, helping convert and format data during mapping so it matches the target system's requirements. They allow users to perform complex formulas and value transformations during the mapping process.
Webhook	An event-driven HTTP callback that enables real-time communication between systems to send or receive data updates based on a trigger event.
Trigger	The event that starts a flow execution. Triggers can be scheduled (time-based) or real-time (event-based).
Pagination	A technique to retrieve large response datasets in smaller, manageable batches to improve performance and reduce server load.
Rate Limiting	A restriction on the number of API requests that can be made within a specified time period, used to prevent system overload.
Concurrency	The ability to control and run multiple API calls simultaneously in parallel.
Data Hub Storage	A repository within Studio that allows users to store and retrieve data temporarily or permanently for use across flows and integrations.
Data Hub Mapper	A repository within Studio that stores reference data in a structured table format, used primarily for lookup operations. It enables mapping between source and destination values for data transformation purposes.
Execution Log	A detailed, real-time record of each transaction. It allows users to monitor the status of each execution (successful, failed, or in progress) and drill into step-by-step details to identify exactly where and why an issue occurred. Users can filter logs by date and status, and view input and output data at each step.
Version	A snapshot of a flow's configuration at a specific point in time. Version control enables users to track changes to flow logic over time and restore previous configurations.
Logic Processors	Built-in components that perform data processing, transformation, and business logic operations within flows. Includes: Filter, Delay, Iterator, Aggregator, Flow Path, Summarize, Set Variable, Data Looper, and XML Converter.
Error Handling	A mechanism to detect, manage, and resolve errors that occur during flow execution. This includes sending notifications, logging errors, and implementing auto-recovery procedures based on error classification.
Flow Timetable	A feature that allows users to schedule the execution of integration flows using predefined intervals: Once, Daily, Weekly, Monthly, or Custom.
Low-Code / No-Code	Development approaches that require minimal or no programming knowledge, allowing users to create and deploy workflows through visual interfaces and drag-and-drop functionality.

Note: This terminology guide is regularly updated to reflect the latest features and capabilities of Reachware Studio.