System
In this section, you will gain access to the platform and licensing information.
System Information
In this section, license and system information of the environment will be listed down.
License information is useful to determine the validity of license and the current state of the platform.
System information details such as Java version, system key, Joget build version, Joget runtime configuration, etc. Such information would be necessary to facilitate technical teams to understand the system environment and help diagnose/pinpoint possible issues.
User Interface Settings
| Name | Description |
|---|---|
| Default Userview | Defines which App's Userview to be shown as the default / App Center when end user accesses the Joget Workflow platform (e.g. mydomain.com/jw ). Typically, you can point to your own App's Userview with your company's branding. New Feature This is a new feature in Joget Workflow v6. |
| Landing Page | Change the default landing page apart from the App Center. |
| System Time Zone | By default, Joget will use server's timezone. You may override it with your own desired option. |
| | By default, Joget will use server's locale. You may override it with your own desired option. (Related: Manage Messages) |
| | By default, Joget will use " dd-MM-yyyy hh:mm aa " as the date format. You may override it with your own desired option. |
| If checked, Joget will use the date format of the System Locale set above, overriding the set above. | |
Enables locale selection to users through User Profile. | |
| | Selection of locales available to users. ("Enable User Locale Selection" must be active first.) |
Enable RTL support. | |
| | Custom CSS file to replace the default look and feel of the web console. (Default CSS file resides at /jw/css/v3.css) |
| | Inline custom CSS to be appended into the web console in addition to the default/CSS URL. |
| Determines if user defined HTML input value should be rendered in Datalist listing. |
Timer Settings
| Name | Description |
|---|---|
| Process Deadline Checker Interval (in seconds, 0 to disable) | Interval checking in seconds for the Deadline elements. Disabled by default. When will deadlines actually get triggered? Deadlines do not get triggered immediately based on what is set in the process design. Instead, deadlines that are due will be picked up in batches based on the interval set here. For example, with deadline checker interval set to 3600 (One hour), deadline of an activity may take up to 1 hour too to get actually get triggered even though the deadline is set to only 5 minutes. Important Do not set the interval to too low (i.e. 1 second) as this may unnecessarily impose high load on the application server as well as the database server.
|
System Administration Settings
| Name | Description |
|---|---|
| | Master Login credential for API call. Please see JSON API Authentication. |
| | Master Login credential for API call. Please see JSON API Authentication. |
| Uploaded File Storage Base Path | System path to store uploaded users' files. |
| | Workflow Designer Base URL. Defaulted to current Joget server path. |
Delete process instance data on when process instance comes to an end. | |
| | SLA indicator level. Please see Defining SLA Indicators. Default: 20. |
| | SLA indicator level. Please see Defining SLA Indicators. Default: 50. |
| | . Default: No Limit. The limit is applied on individual file. Example, if the value set here is 1 (1MB) then one may upload multiple files in a single form with total exceeding 1MB but individually, each file must not exceed 1MB. |
| Disable Performance Analyzer. | |
| | Minimum threshold before showing the Performance Analyzer information. |
| API Domain Whitelist (Separated by ';') | Domain whitelist to allow API calls to Joget Workflow. Example "localhost;www.joget.org;dev.joget.org”, or "*" to allow from everywhere (the behavior from previous releases). |
More Related Articles