When building Frends Processes and Subprocesses you will need to configure Tasks to tell them what they should exactly do. Examples of this kind of configuration could be configuring the SQL query 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 located on the top side of the parameter editor:

These basic properties include:


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.

Condition branches are a special case when it comes to unique naming - the names of Condition Branches only have to be unique for the Exclusive or Inclusive Decision it's attached to. 

Elements that do not have a name input can still be named by double clicking on the element in the editor, but it will only used for display purposes.


For elements of type Start, Task and Call Subprocess a type selection must be done. Clicking on the type selector drop down 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 a selected type. 


Each element also has an optional description field where you can enter free-form 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 etc.

Promote result

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

Activate promoted result by toggling on Promote result as and entering a variable name 

Retry on failure

Tasks can have automatic retries.

Did this answer your question?