resource

Users

Tagged on #feature, #resource,

Sat, Nov 20, 2021

A User account is based on a unique email address. Identification is made using a hashed password in database. This is not possible to register twice the same email address. Additionally, there is currently no way to share resource across User Accounts. :-( (it was the purpose of "permissions" attribute on Flows but the feature is deprecated).

Read more →

Units

Tagged on #feature, #resource,

Sat, Nov 20, 2021

Units on t6 are grouped into various Systems and Types

Read more →

Decision Rules

Tagged on #feature, #resource, #engine, #rules,

Sat, Nov 6, 2021

Decision-Rule is the event-based engine that trigger Actions following matching Conditions. Engine is watching for fact matching conditions on payloads coming from Datapoints POST, and handle Action(s) according to rules.

Read more →

Flow

Tagged on #feature, #resource,

Tue, Jul 6, 2021

Flows are datastore/containers to save and store time/values (called Datapoints). Each Object can send Datapoints to multiple Flows. Flows are defined for each Users and are having permissions. Communication becomes easy in the platform with Timestamp-ed values. Flows allows to retrieve and classify data. Objects are sending their Datapoints to Flow-containers using the API.

Read more →