How to configure a Task

Configuring a Task is as simple as it gets. The first step is to determine what the Task should do. After that, we need to select the Task from the Task selector, as shown in the image below. Frends has multiple ready-made Tasks available for different use cases. To find a specific Task, you only need to start typing the Task's name or scroll down to see all the Tasks available.

All Tasks have the same advanced settings, where you have the option to create a test for the Task and give it a description. You can also choose whether to skip logging the result and parameters, dispose at the end of the scope, promote the result as a promoted variable, or retry on failure. You can access the advanced settings by clicking the "Show advanced settings" button.

However, every Task has its own set of parameters, options, and properties. You can always check for more info on the Task on the Task's GitHub repository page. Usually, the Task parameters tell you, either with an example input or by hovering your mouse over the exclamation mark beside the parameter name, how to use it and what value it expects. Task parameters have different modes, which can be switched by hovering your mouse in the top-right corner above the input field. Usually, these modes are Text, XML, SQL, JSON, and Expression. The first four are quite self-explanatory, but the last one, Expression, means that you can input pure C# code into the input field. When Expression is enabled, you can also reference previous steps in the Process with the #var, #env, #trigger references. You can also put C# code and Process step references without enabling the Expression mode, but you need to wrap these in double brackets like: {{ #var.testVariable }}. This enables you to write text combined with code elements or references.

After you have successfully added your new Task to the Process, you need to attach it either to the next Element or to the Result Element. To learn more about how Tasks can be added to your Process.

The next article is Example on Testing your Task