Flowics Glossary — Key Terms

Additional data fields that extend a Data Connector beyond its default schema. Augmentations are commonly used to add custom properties to sports data connectors and other external data sources.
​

An XML-based syndication format used to connect external content to Flowics graphics. Atom Feeds are supported as a Data Input type.

A reusable UI element that can be added to a graphic, such as:

Building Blocks are the fundamental components used to create an Overlay.

An industry term for a small, persistent on-screen graphic, typically a channel logo, score indicator, or watermark displayed in a corner of the screen.

In Flowics, a bug is created as an Overlay.

The original graphics control interface in Flowics.

Overlays are triggered manually, and content updates require clicking the Update Output button.

See also: Rundown Control.

The REST API used to control Flowics graphics programmatically. It allows external systems to:

Base URL

See Integration ID.

A desktop application that connects local data sources to Flowics through the Middleware.

Common use cases include:

Data Bridge is used when data cannot be accessed directly from the cloud.

A pre-built integration with a specific data provider.

Examples include:

Data Connectors automatically retrieve and populate data within graphics.

A cloud-based endpoint that receives data pushed from external systems.

Supported types include:

A source that supplies data to graphics in real time.

Examples include:

A Building Block that displays a repeating collection of items from a data source.

Common examples include:

The web-based design environment used to create and manage graphics.

Within the Graphics Editor, users can:

A container that holds all graphics for a specific use case, including:

Each Graphics Package has its own output URL and can connect to multiple data sources.

The API credential associated with a specific Graphics Package.

The Graphics Token is required when making Control API requests and can be found under:

Workspace Settings → API Token

A custom identifier assigned to a text, image, color, or other controllable element within the Graphics Editor.

Integration IDs allow elements to be updated through the Control API.

To assign an Integration ID:

Inspector → Show on Remote Control → Control API ID

Also known as a Control API ID.

A Windows desktop application that connects local data sources to Flowics.

Middleware is required for:

A data source configured within the Middleware.

Examples include:

Middleware Sources send data to Flowics through the Data Bridge.

A component of the Viz Flowics Middleware that enables integration with newsroom computer systems (NRCS) using the MOS protocol.

The internal identifier assigned to an element in the Graphics Editor.

Node IDs are visible in editor URLs, for example:

Node IDs are different from Integration IDs and should not be used in Control API requests.

For API control, use the Overlay ID returned by:

A live-rendering URL for a Graphics Package.

Outputs are loaded into production systems such as:

A single Graphics Package can have multiple Outputs.

A configuration that controls which Regions and Overlays are visible within a specific Output.

Output Profiles are commonly used to create multiple variations of the same Graphics Package for:

An individual graphic within a Graphics Package.

Examples include:

Overlays can be triggered independently.

See Graphics Package.

The top-level container used to organize Graphics Packages.

Projects:

The action that makes changes visible in live Outputs.

Until a Graphics Package is published, changes are only visible in the editor preview.

A layout container within a Scene that defines where overlays appear on screen.

Regions can be:

The operator-facing interface used to manually control graphics during a live production.

Remote Control allows users to:

A playlist-based control interface where graphics are organized in a running order and triggered sequentially.

Commonly used in:

A design canvas within a Graphics Package.

A Graphics Package can contain multiple Scenes, each with its own layouts, Regions, and Overlays.

Serial Digital Interface (SDI) is a professional video transmission standard that carries video signals over coaxial cable.

Flowics supports SDI output through:

A label assigned to a Region or Overlay within the Graphics Editor.

Tags are commonly used to associate content with specific Output Profiles.

See Graphics Token.

Your organization's Flowics environment.

A Workspace contains:

All resources belong to a single Workspace.

Can't find a term you're looking for?

Contact the Flowics Support team at:

support@flowics.com