Skip to main content
Parameter Editor

General element configurations.

Ossi Galkin avatar
Written by Ossi Galkin
Updated over 6 months ago

When building Frends Processes and Subprocesses, you will need to configure Tasks to define exactly what they should do. An example of this kind of configuration could be configuring the SQL query that an SQL Task should execute.

The configuration of these Tasks is done using the Parameter Editor, which appears on the right side of the Process Editor when selecting a Task from the Canvas.

Configuring Element Basic Properties

When configuring Tasks using the Parameter Editor, you should start with the basic properties.

Name

Many Elements have a name input. Elements with return values generally require a name. The Element name is used when referencing the result of a previous Element, and therefore, the Element name must be unique within a Process.

Type

For Elements of type Start, Task, and Call Subprocess, a type selection must be made. Clicking on the type selector dropdown will show a list of available types. After selecting a type, the parameters associated with it will be displayed. The Task return type and package can be seen by hovering over a selected type.

Description

Each Element also has an optional description field where you can enter freeform information or documentation about the operation the Task is performing. This is a good place to store, for example, contact information of a specific system holder if there is a problem executing the Task.

Retry on failure

Tasks can have automatic retries.

Dispose at the end of the scope

When activated, the result object will be disposed at the end of the current scope.

Promote result

Elements of type Return, Intermediate Return, Task, Call Subprocess, and Code have the option to promote the result. To activate the option, simply toggle "Promote result as" and enter the variable name to be used.

Did this answer your question?