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

Logs

In the Logs area, all logs older than a selected date can be deleted and also there could be set a configuration for automatic deletion of the execution logs and local log files.

The execution logs and local logs automatic deletion can be set by enabling the Enable automatic log clearing option and selecting one of the following options and configuring the X value:

every X days: for example, if X is 5, the execution logs and local log files will be deleted every 5 days
every X months: for example, if X is 5, the execution logs and local log files will be deleted every 5 months
older than X days: for example, if X is 5, the execution logs and local log files older than 5 days will be deleted
DB size bigger than X GB: for example, if X is 10, the execution logs and local log files will be deleted when the database size will reach 10 GB.

After setting the value for X, click the Apply button for the settings to be saved.

IMPORTANT: the Workflow Execution Logs will be deleted in chunks, with the initial value set to 500 items. For smaller amount of logs the default value can be changed in the Scheduling's service configuration file, which can be found at C:\Program Files\Flowster Solutions\Flowster Studio\Scheduling\, the appsettings.json file, ItemsTake:

"ClearLogsSettings": {

"Interval": "1m",

"ItemsTake": "500"

}

There are two configuration options in the Scheduling service settings file which affect the log cleaning process. The "Interval" which determines the interval of time at which the checking for the cleaning process is done and "ItemsTake" which represents the chunk size of how many log entries that respect the condition set in Administrator are taken at once for deletion. The number of execution logs must be greater or at least equal to the "ItemsTake" value for the configured period (e.g. at least 500 execution log entries older than 10 days) in order for the deletion process to start.

Modifying these values is useful when trying to balance the speed and cpu/memory performance of the cleaning process. After editing the values, a restart of the service is required.

Configuration example:

>500 items: the default value can remain the same, 500
<500, e.g. 100 items: the value can be set to 50 (a total amount of 100 logs will be deleted in 2 steps, each consisting in 50 logs) or even 100 (a total amount of 100 items will be deleted in a single step).

Support File

The Support File area allows the export of a .zip file containing Flowster Studio information such as:

Configuration files
Database, local files and event viewer logs
Product version and OS information
Tenants configurations

The Error Logging area allows user to specify where the logs resulted from using Flowster Studio can be written to. By default the logs will be written in the database and they will be visible by accessing the Platform Logs page in Administrator. The Logging to network path will write the logs into a file at the specified network address.

Portal URL

This setting allows users to change the default value (hostname of the first engine) for host URL to which the user is redirected from the approval emails. The default value should be changed if using a DNS alias or a loadbalancer.

Select Engine

In the Engine Selection on Startup area, the user can configure the Administrator to allow the selection of a Flowster Engine, instead of just using the default one. In order to enable this option, check it and click Apply. This setting is made per instance and per user. If the option is enabled, when navigating to Administrator from Portal, the Select Engine window will open allowing the user to connect to a specific engine:

At the first start of Administrator, there will be discovered all engines with matching GUID. When navigating to Administrator again, there will be displayed a cached list with all previously discovered engines. For a new discovery, the Discover button must be clicked.

NOTE: The list of the previously discovered engines is cached so engines which are not available anymore (the service is stopped, Flowster Engine is not installed anymore on a certain machine etc.) might still appear in the list.

Select the desired engine (if only one is installed, then select the single engine from the list) and click OK.

If needed, DNS inputs can be used.

The manual inputs field is used to check if a Flowster Engine is reachable or not by clicking Check.

For creating a DNS endpoint the following steps need to be executed:

Open control panel and go to: Control Panel\All Control Panel Items\Administrative Tools
Click on DNS and a message box to choose the DNS server will pop up.

After choosing the Windows DNS Server a new window containing DNS Manager will appear. Go to the path you want to add the endpoint. Right click and select “Other New Record”
Select “Service Location(SRV)” as a resource record type

Add correct endpoint data and save entry

When opening administrator choose DNS and add SVR Record path. Click Refresh

Select endpoint and click on Save Changes. Administrator should open with the selected endpoint. If engine doesn’t exist then Administrator will open with default configuration and if engine exist and user has no rights then the no rights error message will show and Administrator will not open. The engine endpoint format should be with IP or with the machine’s name.

Default Tenant Language

There are currently 2 options available for default language that can be set: english and german.

Select Language for current tenant and click Apply.

Default Tenant Landing Page

The user can set the default entry page of the portal , which will see after the login. After selecting the page and category, save your settings by clicking apply. This setting is saved per Tenant.

If the user have no permission on category page, in the Select Category field will appear Restricted Category.

Clear logon sessions

This setting clears portal sessions, admin sessions or both depending on the selection.

After selecting the Session type and Older than , save your settings by clicking apply.

This setting is available only for superadmins.

Auto Assign to workflow scheduling

The customer can activate or deactivate in this area a flag to auto assign a new activated timestamp of a workflow to an existing workflow scheduling.

If there is a scheduled workflow timestamp and the user activates another timestamp of the same workflow, and this option is activated, the scheduled workflow will change to the newly activated timestamp automatically.

Note 1: the customer will get a warning if the arguments of the new activated timestamp don’t match the previous timestamp.

Note 2: The default Value is set to False.

Browser not supported