Project parameters

Parameters let you reuse one workflow with different values without editing the graph.

Create a parameter

The parameter manager can define, among others:

• text;
• integer or number;
• boolean;
• choice list;
• source or destination file;
• directory;
• CRS;
• password.

Each parameter has a stable internal identifier. Its displayed label can be more user-friendly.

Bind a parameter

A configurable value can reference a project parameter with the @{identifier} syntax or through the controls provided by the interface.

For files and directories, use the dedicated bindings rather than manually constructing ambiguous paths.

Values at run time

Parameters marked Show at run time appear in the run dialog. Values entered for one run do not necessarily change the value saved in the project.

Choice lists can display a label that differs from the actual stored value.

Secrets

A password parameter is not intended to be stored as plaintext in the project.

For PostgreSQL connections or map-service credentials, Catenivo uses the operating-system credential store when available:

• Windows: native credential vault;
• Linux: Secret Service compatible with GNOME Keyring/KWallet.

When no vault is available, Catenivo keeps the secret in session memory and does not offer a plaintext fallback.

CLI

The CLI accepts parameters with --param identifier=value. For secrets, prefer --param-env identifier=ENV_NAME so the secret value does not appear in the command line.

See Command line.