The Start block is always the first block in the Workflow Editor and the workflow's basic functioning depends on it. It is used for inserting variables which can be assigned to and used in various ways by other blocks.
Click "+Add Variable" to create and set as many variables as is needed for a workflow.
All variables have a Name and a Default value and can be either Inputs or Outputs. While values are surrounded by quotation marks, names are not.
The Start block also features a "Description" field. This is the description of the whole workflow, which can be given either on the Workflows page or directly on the Start block.
The Manual Execution Time (MET) option is used to simplify reports on the Return on Investments (ROI) calculation. It shows you the time in minutes that is saved by running a workflow as opposed to completing the task manually. You can choose between a default automated MET calculation and a manually inputted MET calculation.
The option to choose a worker group that aids in the task-completing process and observes the state of the flow is also available.
Checking the "Advanced" box expands the block with additional options for any given variable: "scope", "type", and "required.”
The cURL provides a sample of the RESTful endpoint for a specific workflow. If the variables are defined, they will be present in the sample as well.
When "Required" is checked, it guarantees that the variable will be shown.
Type is used to set the type of the variable (string, boolean, integer, double, object, etc.)
Scope is used for setting the visibility of the variable. The scope is the space (area) in which a variable exists. Beyond its scope, a variable will not be recognized.
The variable is local for each task. Any change to the local variable is reflected upon all subsequently linked tasks.
Example below: We have two child blocks of A1 - A2 and A2. In each of them, the X variable changes its value independently from 1 to 2.
The variable is common for one active process. Two processes that are active at the same time have different intermediate variables but all parallel tasks within one process have one and the same shared intermediate variable.
Example below: We have two parallel processes (A1, A2, A3 on the left and A1, A2, A3 on the right) where the Y variable goes from 1 through 2 to 3.
The variable is common within the system. Currently, it's on a Worker level but the variables will soon be synchronized between workers as well. Any change from anywhere is reflected upon all other active or future processes.
Example below: When we have a change of the value of the variable Z, no matter where in the flow, the change is taken into account by the next block that makes a new change of its value. The Z variable goes from 1 to 6.