FlowWright engines have various configuration settings that many of its engines use to function.
You must navigate to the Status - Status page.
Select the Settings - Configuration menu option.
The application Config Settings UI is rendered below. The engines read configuration settings at start-up and every 5 minutes. Engines can auto-configure themselves at runtime based on the configuration provided.
Workflow Engine Service.
All dates and times are stored within the database as UTC and displayed based on the user's local time zone.
Note: Engine runtime data are in ISO + UTC format.
Artificial Wait time—if the workflow goes into an endless loop or the number of continuously executed steps is equal to the engine's long-running step cut-off limit, then the engine automatically puts the workflow instance into a 100-second wait.
Engine service interval—This interval is used to determine how often the engine checks for work from the database. With a configuration of 500ms, the engine checks for work every 1/2 second.
Engine processes—the maximum number of child processes to launch to process workflow. By default, it has 5 child processes; increase this based on the environment's resources.
Engine service max for no work—This value is used if the engine has no work. Normally, the engine checks for work every 1/2 second. If there's no work to be done, the engine starts checking every 1 second. As soon as there's work to be done, it will change to using the 1/2-second check.
ESB Engine Service
The ESB engine has settings similar to those of the workflow engine.
Email Service
The email services uses the below settings to send and retry emails.
Archival Service
The archival service runs every hour but processes archival based on the configuration values that are configured for archival.
Statistical Service
The statistical service runs daily and collects statistics on processes.
Trigger Service
Trigger service uses the configuration from each of the triggers configured within FlowWright.
DFS Service
Distributed file system service synchronizes files across distributed servers using the following configuration within FlowWright