Project Parameters

In the GRAVITY system, each project (application) can be enhanced with a set of project parameters, which act as additional variables controlling data flow and operator logic within the project. They are independent of the source input data and can be used in multiple places simultaneously, which increases the flexibility, readability, and modularity of integration projects.

Main Features of Project Parameters:

They can be manually declared by the user during project creation or editing.
Their value can be passed:

manually by the user during manual project execution (displayed in the start-up form),
automatically by a trigger, which passes parameters when invoking a project (e.g., from an HTTP request in a WebService),
internally by a special OUTPUT PARAMETERS, operator that calculates or passes the parameter value forward.

Parameters are visible in operator configuration and can be used, for example, to:

dynamically filter data,
control project logic (e.g., conditional data flow switching),
define data sources or output paths,
enable communication between operators.

Typical Uses of Parameters:

Providing a customer ID to be passed into an SQL query.
Defining the data processing date (e.g.,dataOd, dataDo).
Controlling the project mode (e.g., test or production).
Specifying the file location from which data should be retrieved.

Parameter Configuration

You can view the global list of all parameters by clicking the icon on the Toolbox element.

The parameter list is divided into object groups in which each parameter has been defined.

Each parameter has a specific type, which determines how it can be used in system operators. It also has a name and description, can have a defined default value, and can be marked as required.

If the system does not receive a value for a required parameter during process execution, it will report an error.

Available Parameter Types:

String → any text string
Integer → integer numeric value
Double → floating-point numeric value
DateTime → date with time (if only the date is provided, the time will default to 00:00:00)
Boolean → takes the value true or false
Blob → binary value
ArrayString → array of text strings in the format ["item 1", "item 2"]
ArrayInteger → array of decimal values in the format [2,3,4,5]
ArrayDouble → array of floating-point values in the format [1.1, 1.2, 2.1]

Example of Using a Parameter in a Project

Many operators in the GRAVITY system allow parameters to be used during process execution. By reviewing the operator definitions, you can learn how parameters are used across different operators. Below are two examples illustrating the general concept:

in the SQL INPUT operator:

in the COMPUTING operator:

Example of Trigger Invocation with Parameters

In a trigger invocation via REST API:

In a PostgreSQL database notification:

The pg_notify function should include a JSON object as its second parameter, structured according to the parameters of the process being invoked:

{ "id": 23 }

To learn how to pass parameters onto the data bus as data bits, see the

INPUT PARAMETERS section.

To learn how to set or modify a parameter value during process execution, see the

OUTPUT PARAMETERS operator.