Core terms and concepts

When you create a ManyWho account, you are assigned a tenant where your builder information, flows, content, metadata, assets, and service integrations are stored. A tenant is an user of a software application that serves multiple other users as well. Each tenant’s information is invisible to other tenants.

The ManyWho tenant is associated with your email address. You can add multiple builders to a tenant and collaboratively build flows with other members of your team.

A subtenant is a new tenant under the same tenant account. Subtenants do not have visibility into the content, flows, values, or service integrations of the tenant (and vice versa).

You can use different subtenants for different divisions of your company. For example, separate subtenants for HR and Accounting. Subtenants can also help to organize your project, for example, you can logically separate out deployment environments into Development, Staging, and Production.

Builder

A builder is a person building flows. A tenant can have multiple builders.

User

The person who uses or will use the app you built using ManyWho.

Drawing Tool

The Drawing Tool is the ManyWho drag-and-drop environment where you build flows, add subtenants or builders, install service integrations, and run/publish your flows.

Procedures

Canvas

When you are building an app with ManyWho, the canvas is where you will build the flow.

Procedures

Flow

A flow (or a flow diagram) is how you build your app in ManyWho. Once you have diagrammed your business process on the Drawing Tool canvas, the ManyWho Engine converts it into a working app.

An element is a building block in your flow. Elements are categorized into map, group, shared, and navigation elements based on how they are used.

Procedures

Map element

An element is a building block in your flow. Elements are categorized into map, group, shared, and navigation elements based on how they are used.

Procedures

Group element

An element is a building block in your flow. Elements are categorized into map, group, shared, and navigation elements based on how they are used.

Procedures

Shared element

An element is a building block in your flow. Elements are categorized into map, group, shared, and navigation elements based on how they are used.

Procedures

You can use the navigation element to build non-sequential workflows with ManyWho, where flow control passes from one element to another without waiting for a previous element to be executed.

Step element

You can use the navigation element to build non-sequential workflows with ManyWho, where flow control passes from one element to another without waiting for a previous element to be executed.

Page element

You can use the navigation element to build non-sequential workflows with ManyWho, where flow control passes from one element to another without waiting for a previous element to be executed.

Decision element

You can use the navigation element to build non-sequential workflows with ManyWho, where flow control passes from one element to another without waiting for a previous element to be executed.

Procedures

Operator element

You can use the navigation element to build non-sequential workflows with ManyWho, where flow control passes from one element to another without waiting for a previous element to be executed.

Procedures

Message element

You can use the navigation element to build non-sequential workflows with ManyWho, where flow control passes from one element to another without waiting for a previous element to be executed.

Procedures

Database Load element

You can use the navigation element to build non-sequential workflows with ManyWho, where flow control passes from one element to another without waiting for a previous element to be executed.

Procedures

Database Save element

You can use the navigation element to build non-sequential workflows with ManyWho, where flow control passes from one element to another without waiting for a previous element to be executed.

Procedures

Database Delete element

You can use the navigation element to build non-sequential workflows with ManyWho, where flow control passes from one element to another without waiting for a previous element to be executed.

Procedures

Service element

You can use the navigation element to build non-sequential workflows with ManyWho, where flow control passes from one element to another without waiting for a previous element to be executed.

Type element

You can use the navigation element to build non-sequential workflows with ManyWho, where flow control passes from one element to another without waiting for a previous element to be executed.

Procedures

Macro element

You can use the navigation element to build non-sequential workflows with ManyWho, where flow control passes from one element to another without waiting for a previous element to be executed.

Procedures

Outcome element

Outcomes connect elements in the canvas and show how a flow progresses. In your app, the outcomes get converted into clickable buttons. Some elements (like Load or Save, that handle backend database actions and are not visible in the front end), do not have any buttons that are visible in the app, but must still be connected using outcomes.

Tag element

You can use the navigation element to build non-sequential workflows with ManyWho, where flow control passes from one element to another without waiting for a previous element to be executed.

Procedures

Values in ManyWho are similar to variables in the programming paradigm. They are containers that have a name, and contain data. This data can be numbers, text, dates, instances of a type (say, Type: Customer), or another value.