The status UI displays various configuration information for FlowWright, such as version information, licensing, settings, and upgrades. Each menu item renders status information.

Version

Click the respective buttons to view the FlowWright version number, access version history, upgrade information, and instructions.

Click on the "View Version History" button to learn about past versions of FlowWright. 

Tenant Information

You can view the tenant name, ID, APP URI, and REST API URI details here. The tenant name is also displayed in the user information area. 

Culture and Timezone Information

This displays the culture setting used by the application's back end, user interface, and engines. Based on the culture selection, the UI will also display the date/time according to the culture formation. 

The user may change the application's culture according to their respective region. The user should log in to the application again for changes.

The user may change the time zone according to their respective region. The changes will take effect after the user logs in to the application again.

Database Information

Displays database connection string used. FlowWright's standard database runs on Microsoft SQL Server, and FlowWright also supports Microsoft Azure DB for cloud environments.

Service Status

It displays the engine services and their statuses. FlowWright is powered by six high-performance engines.

• Process engine
• Enterprise service bus engine
• Archival engine
• Statistics engine
• Trigger engine
• Email engine

Each engine has its configuration settings. These engines launch robotic worker processes to perform the work. All dates/times are stored within the database as UTC and displayed based on the user's local timezone. 

Note: Engine runtime data are in ISO + UTC format. 

The pulse action animation indicates that the service is running, and the play graphic indicates that FlowWright Admin must manually start it.

Settings Cache

What's this cache for?

To improve the application's performance, FlowWright caches some of the configuration information. Any changes to the configuration are automatically cleared, and the cache is rebuilt. The contents of the cache can be downloaded or removed using the buttons. 

How often should we clear the cache?

We advise against clearing the cache unless required—for example, when the process step does not reflect the new changes updated through the patch release.    

Are there any performance issues on the user side?

The settings cache is used when the application runs for the first time. As such, there are no performance issues on the user's side. 

Master Script (for Form Widgets)

We advise updating the master scripts file once after every patch release update. This action keeps the event scripts configured for form control updated. 

Process Request Queue

The request queue displays a summary graph based on the status of engine alerts.  

Click on “View Engine Alerts” to display a list of engine alerts:

The engine alerts can be filtered by type and status. Select the Type from the drop-down list below. 

Select the Status from the drop-down list below. 

You can use the Clear menu to remove engine alerts as required. 

Restart Application

Restarts the IIS web service and relaunches the FlowWright web application. 

An alert notification confirms that the application has been restarted. The user should exit the browser tab and log in to the application again.