Frends Glossary

All the terms Frends uses, and what they mean.

In this glossary we gather the specialized terms and concepts that reflect the technologies and methodologies we employ. Our vocabulary is designed to align with our innovations, enhancing clarity and collaboration within our platform, while keeping things simple and friendly.

Integration terms

Here's a list of key terms used during integration development in Frends, and whenever discussing about details of an integration flow.

Process

A sequence of tasks executed in a defined order to achieve a specific integration goal. Otherwise called integration flow, logic or sequence.

Subprocess

Reusable sequence of tasks, created in the same way as Processes. Subprocesses can be inserted into Processes as Task-like shapes, and reused in multiple Processes.

Long-running Process

Long-running Processes are sometimes called orchestrations or stateful workflows, where the execution might stop temporarily to wait for external processing. Unlike separate Processes, the Long-running Process remembers the state it was in and the data processed, so it can seamlessly continue from where it left.

Shape

Any element in a Process is called shape. As the Processes are created using BPMN notation, the elements added to the Process are shapes.

Sequence Flow

Arrow connecting different Tasks together in a Frends Process, to form the integration flow. Not to be mixed up with connectors from other integration platforms, which are Tasks in Frends.

Task

A single operation or action within a Process. Comparable to a connector in other integration platforms. Can be pre-defined action as Task or more custom when using Code Task.

Trigger

A mechanism that executes a Process based on specific events or conditions, like schedule or an incoming message.

Parameter

Input values that modify and control the execution of Tasks and Processes.

Code Task

Shape in Process that contains a multiline C# code statement. Can be used to create custom functionality within Process, that is not otherwise possible to perform using the provided Tasks or other logic. Commonly called Code Block or Code shape.

Assign Variable

Shape in Process that contains a single expression of C# code. Can be used to assign variable a value using C# code or text, or modify existing variable's value. Also called Expression shape.

Handlebars

Frends allows inserting C# code expression's result into any text content using Handlebar ( {{ }} ) notation. Code inside Handlebars is compiled during Process save, but the value itself is evaluated at runtime.

Scope

Shape in Process that can contain other shapes. Can be used to arrange Process flow into logical sections as well as implement error handling for the contained logic. Different Scope shapes, Foreach and While, can be used to perform iteration within Process.

Process Instance

Single execution of a Process.

Reference Values & Variables

Variables and values that are accessible in expressions through hashtag (#) references, such as #var, #env, #result, #trigger and #process.

Variable

Variables that are defined in the Process during execution. Accessible in expressions under #var reference.

Process Variable

Process-specific variables that are defined for a Process to have value right at the beginning. Accessible in expressions under #var reference. Can be changed during Process execution.

Environment Variable

Centrally managed, globally available variable, that has different values for each environment. Accessible in expressions under #env reference.

Trigger Variable

Values that are provided in variable-like style from the starting Trigger shape. Accessible in expressions through #trigger reference.

Process Instance Variable

Process Instance variables contain instance-specific data, such as execution id. Accessible in expressions through #process reference.

Promoted Value, Promoted Variable

Value or variable specified within Process, that will be shown in the Process Instance list and logging. Monitoring Rules can be set to target and monitor these values as well.

Execution environment terms

Instead of runtimes, nodes and servers, Frends uses the terms below to mean the parts of an execution environment.

Environment

A distinct set of values and configuration that form environments such as Development, Test or Production. Environments contain one or more Agent Groups and provide them a common set of values as Environment Variables.

Agent Group

A set of Agents running the same Processes using the same settings. Agent Group can have one or more Agents in them.

Agent

A runtime environment where processes are executed. Analogous to a server, node or runtime in distributed systems. A single server is allowed to host multiple Agents.

High Availability, HA

Or High Availability confirguration, HA configuration. Specific setup using multiple Agents in one Agent Group, executing the same Processes with same settings and data. Allows Process executions to continue even if one or more Agents are not available or busy, and ensures there's enough resources to handle all processing.

Gateway Agent

Agent acting as an API gateway, publishing the API endpoint in a load balancing manner. Does not directly run Processes, instead forwards the API requests to other Agents for execution.

Tenant

Your very own execution and management environment to Frends. Includes the Agents, Environments and Control Panel with all of its tools. Your Frends Tenant is identified by its url, at yourtenant.frendsapp.com.

Frends UI

Frends Portal

Your portal to accessing all the Frends Tenants you have access to, as well as for managing your Frends plan.

Frends Control Panel

The main user interface for your Frends Tenant. In here you can manage your APIs, Processes and Agents.

Startpage

Page you arrive on when accessing your Frends Control Panel, containing the global search, onboarding materials and documentation.

Dashboard

View with collection of widgets that you can set up to monitor your Frends Tenant and its Processes.

Process List

List of Processes deployed to the chosen Agent Group. From the list, you can execute, edit, manage and view logs for the Processes.

Subprocess List

Same as Process list, but for Subprocesses.

Process Editor

Integration flow editor, built in to your Frends Control Panel.

Process Instance List

Lists the executions for the chosen Process during the specified time span.

Process Instance View

Shows the details of a single execution of a Process in visual format.

Monitoring Rules

Feature in Frends that allows creating rules for monitoring Process Instances. Can be used for example to monitor that there are enough Process executions for a given time period, and notify interested parties if not.

Frends API terms

API management is built in feature of Frends.

API Management

Feature in Frends which allows you to create REST APIs from OpenAPI specifications, and then connect endpoints of those APIs to Processes for performing the actual logic behind those endpoints.

Passthrough API

API endpoint specified to Frends, but instead of containing Processes for logic, the requests are forwarded to another system for handling. Could also be thought of as API proxies.

API Policy

Set of rules and specifications that are connected to the APIs in Frends. They can be used to set up authentication as well as logging rules for the incoming connections to your Frends Tenant.

Frends Add-On Products

In addition to Frends iPaaS product, Frends offers add-on products that can be used to enhance the Frends experience.

Business Application Portal

Simplified, no-code interface aimed at business users to run and manage integrations. ISVs and SaaS partners can use it to provide embedded iPaaS and IaaS solutions to customers with white-labeling options.

API Portal

Allows you to create API products using Frends API Management features that can be published in the API Portal for an API developer self-service experience.