The Settings → Execution Agents page can be reached by clicking the menu item.

In the Groups area a list of the execution groups is displayed.

Execution Groups are user defined groups where the Execution Agents are inserted. Multiple agents can be part of the same execution group.

Add Execution Group

An Execution Group can be added by clicking the Add button, which will open the Add group window:

Add a name for the group. In the example above there is a machine name
Click Save Changes in order to add the new group or Close.

After a group is created, it will be visible in the Execution Groups list:

Other operations that can be made over an Execution Group can be Edit or Remove.

Edit Execution Group

In order to edit an execution group, select it and click the Edit button:

There can be changed the name of the group and
Click Save Changes to save the new information.

Delete Execution Group

In order to remove an execution group, select it and click the Remove button.

NOTE:

The Execution Groups cannot be removed or edited if they are already assigned to one or multiple workflow timestamps.

Add Execution Agent

An Execution Agent’s displayed information are:

Execution Agent's endpoint: the address of the execution agents, in the 0.0.0.0 format or MACHINENAME format
Score: obtained by the Execution Controller service
Groups: the Execution Group where the agent is in
Agents Actions: the available actions for an endpoint are Add, Edit and Remove. Removing an execution agent will delete the agent’s information from the database.

Execution Agents are Flowster Studio’s custom services which executes workflows on demand. Execution Agents are used when launching a workflow into execution from Portal or Designer.

An Execution Agent is installed by using a custom installer, which creates an entry into the Flowster’s database, but Administrator allows the user to manually add an execution group into the database or to modify existing agents.

NOTE:

adding an execution agent into the Flowster database does not install the agent itself. Also, removing an agent from the database does not uninstall the agent itself.

A new Execution Agent can be added by clicking the Add button:

Insert the execution agent's endpoint in the 0.0.0.0 format or MACHINENAME format
Select the group where the new execution agent should be added
Select True or False for Use static connection. If Use static connection is true then only one connection will be done and re-used through the app, otherwise, if false, the connection will be recreated every time and closed after each operation.
Click Save Changes in order to save the provided information.

Edit Execution Agent

An Execution Agent can be edited by selecting it and clicking the Edit button:

edit the endpoint
Select a group from the list to change it
Change the Use static connection setting
Activate/ Deactivate the Execution Agent Maintenance
1. Maintenance Set to True = Execution Agent is not active and it can't take workflows from the workflow queue, but the agent service can still be running on the agent server;
2. Maintenance Set to False = Execution Agent is active can be used;

Note1: This option is used for maintenance or debugging.

Note2: The default value for Execution Agent Maintenance is False.

Click Save Changes to keep the new values.

Remove Execution Agent

An Execution Agent can be removed by selecting the agent and clicking the Remove button.

Local Workflow Logging

In order to make visible the Local Workflow Logging area, click on a specific execution agent from the Execution Agent list:

By default, the Logging enabled option is set to Off. When set to On, each execution of the selected workflows from Configuration Items → Local Workflow Logging is logged as txt files under the path specified on Logging Path field (if the inserted path is from a local directory, it refers to the local directory where the execution agent is installed):

Execution Agent configuration settings

There are settings configurable for execution agents in the configuration file that impact the workflow execution process in Flowster Studio:

TerminateHangingWorkflows setting - if set to "true" it will terminate the execution of started workflows in the case of an Execution Agent service failure (e.g. the service stopped, the server was restarted). The Execution Status of the workflows will be updated to Terminated when the Execution Agent service is available again. We recommend to not change the default value.

Assembly dependencies - there can be multiple version of the same library. There can be seen in the configuration file as well. We recommend to not change the default value.

RunningWorkflowsLimit setting - this option limits the number of workflow executions that can be performed in parallel. By default it is set to 10, but is configurable per execution agent (only workflows with Execution Status Started/Running are included in the count). If the execution agent will be heavily loaded with parallel workflow executions, we recommend to lower this value to a value that allows the system to execute workflows with high performance.

NOTE: this setting will be added to the existing execution agents during the upgrade. If an execution agent is not upgraded, it will not contain this setting, therefore no limitation for the number of parallel executions will be taken into consideration.

To change the default configurations for these options:

Navigate to <INSTALL_DIR>:\Program Files\Flowster Solutions\Flowster Studio\NewExecutionAgent
Open ExecutionAgent.exe file and search the "AppSettings" section
Change the key value (TerminateHangingWorkflows accepted values are "true" or "false" )
Save changes
Restart FlowsterNewExecutionAgentService windows service