Data inputs are like containers that hold external data that you will use to create your graphics in Viz Flowics.
When you create a data input, Viz Flowics generates an endpoint (the container) where you can push or stream your data.
To create a data input, on the top bar click on DATA CONNECTORS, select Data Inputs, then click the plus button and select the data input you need to create.
Be aware
Adding new data inputs is restricted to company administrators. Please contact your company admin to add the new input for you.
There are two types of data inputs: generic and custom.
Generic Data Inputs
This type of data input is useful when integrating your data, either through the Data Bridge or your own system that enables data transfer to a Viz Flowics input.
The are two types of generic data inputs:
JSON HTTP Push - Content
JSON Streaming Push - Content
When setting up a generic data input, you will need to generate a data schema. This is a JSON object that defines the structure of your data and helps Viz Flowics map the data to your graphics. To do so paste your JSON data into the example data box and then click on the 'Generate schema from example' button.
If you have already generated the schema, click on 'Direct Input' and paste it there
There are some Data Inputs that allows to editing the schema, and this is to verify the data (only HTTP, not WebSocket) and to make it available for binding primarily.
Custom Data Inputs
Viz Flowics provides custom data inputs to be used with certain data connectors. E.g., if you are using ScoreboardOCR as your data provider, Viz Flowics has custom Data Input designed for this purpose, along with a corresponding native data connector.
Custom data inputs are typically easier to set up than generic data inputs, as you don't need to generate the schema in most of them.
Here is a list of the available custom data inputs:
Data Input | Description |
ASI API - Computed data by activity sink | Connect this data input with Insiders ASI API data connector |
Equipe Timekeeping Client API - Clock | Connect this data input with Equipe data connector |
PUBG Mobile on-premise - API Sink | Connect this data input with PUBG Mobile on-premise data connector. Learn more here. |
Scoreboard WebSocket Integration - Timing & Scores | Connect this data input with Scoreboard OCR data connector. Learn more here. |
Time2Win API - Race Clock | Connect this data input with Time2Win data connector |
Control Access Settings - Optional Settings
When setting up a Data Input (generic or custom), you will find additional settings that are optional but meant for control access purposes:
Control Access - Allowed CORS Origin: This allows data to be pushed from the browser directly to Flowics from other webapps. Can be tested with an
OPTIONSrequest:curl -i -X OPTIONS -Horigin:http://xx -HAccess-Control-Request-Method:POST https://discover.flowics.com/…for more info about the OPTIONS method click here
Control Access - Allowed IP Networks: Allows to receive only data from certain hosts on the internet. The list can contain individual IP addresses (IPv4/IPV6)
192.168.0.1or networks192.168.0.0/24
Understanding Data Flow
Once you have created a data input, you can start pushing data to it. Use an external system that pushes data (via HTTP POST or WebSockets, whether using a JSON Push or JSON Streaming Push data input) to the Viz Flowics input.
This system can be your own app or script, or it can be the Data Bridge that lifts a local JSON and pushes it or connects to a local Rest API.
Data can flow to Viz Flowics in two ways:
Local to the cloud: Data is transferred from a local source to Viz Flowics through the Data Bridge or your own custom app/script that pushes the data to a Flowics data input.
Cloud to cloud: Data is transferred from a third-party data provider in the cloud to a Viz Flowics data input.
Using Data Inputs
To use data inputs in your graphics packages, you will need to create a data connector. A data connector maps the data from the data input to the specific elements in your graphics.
For example, if you have a data input that contains information about sports scores, you could create a data connector to map the data from that input to the score text element in your sports graphics.