Within the detail page, it’s possible to define the configuration of the web action.

By clicking on the “Add Configurations” button shown in the figure, the form for creating the configuration necessary to define the action is opened, as shown in the figure. The form is divided into three parts:

• Configuration Profile
• Request Template
• Template Params

The first part defines the configuration’s profile, with a mandatory name and an optional description.

The second part, “Request Template” allows the definition of the HTTP request to be made. In particular, we can define:

• Headers: By clicking on the “+ " button next to the header section, it is possible to define in a separate form the headers to be included in the request, as shown in the figure below.

  

  The form allows you to add the name and value of the headers that will be added to the HTTP request later.

• Method: The methods available for HTTP request are:

• Url: endpoint for the request

• Body: http body.

• Template Params: By clicking on the “+” icon next to the header, the form for adding the values of the parameters opens. These parameters are dynamic and can be added to the HTTP request.

With this form you can define:

• Name: parameter’s name

• Default value: default value used in case of automatic execution

• Mode:insert mode of parameter. Can be:

  • Manual: the parameter must be entered by the user at the time the web action is executed.

  • Automatic: default value used automatically.

• Mandatory: if the value is mandatory or not