3.2 - Configuration File env.ini

Overview

ProcessMaker uses the configuration file env.ini for global settings that aren't available in the Admin panel.

Editing the env.ini File

Use a plain text editor to edit the configuration file located at:

<INSTALL-DIRECTORY>/workflow/engine/config/env.ini

or:

<INSTALL-DIRECTORY>/shared/sites/WORKSPACE/env.ini

In Linux/UNIX (manual install):

/opt/processmaker/workflow/engine/config/env.ini

/opt/processmaker/shared/sites/WORKSPACE/env.ini

In Linux/UNIX (Bitnami install):

/opt/processmaker-3.X.X.b1-0/apps/processmaker/htdocs/workflow/engine/config/env.ini

/opt/processmaker-3.X.X.b1-0/apps/processmaker/htdocs/shared/sites/WORKSPACE/env.ini

In Windows (manual install):

C:\opt\processmaker\workflow\engine\config\env.ini

C:\opt\processmaker\shared\sites\WORKSPACE\env.ini

The settings in the engine/config/env.ini file are used by all workspaces, whereas the settings in the sites/WORKSPACE/env.ini file only apply to a particular workspace. Settings can added to either file, but a setting in the sites/WORKSPACE/env.ini file will override a setting in the engine/config/env.ini file.

The default content in the env.ini file is the following:

Most of the settings can be enabled by setting them to 1 and disabled by setting them to 0. Settings that are strings should be enclosed in double quotation marks. Lines beginning with ; (semicolons) are treated as comments and are ignored. Remove the semicolon to uncomment the setting.

Available Settings

• debug_sql = 0|1
  Set to 1 to log all SQL queries to the wf_<WORKSPACE> database in MySQL and view SQL error messages in the __ERROR__ system variable in the Debugger. Default is 0. For more information, see the MySQL Logging section.
• debug_calendar = 0|1
  Set to 1 to log information about calendars. Default is 0.
• default_lang = "LANG"
  Example: default_lang = "es"
  Sets the default language of ProcessMaker at the login screen. When the web browser is directed to http://IP-ADDRESS, it will automatically be redirected to http://IP-ADDRESS/sysworkflow/LANG/SKIN/login/login. If not set, then the default language is "en" (English).
• default_skin = "SKIN"
  Sets the default skin of ProcessMaker at the login screen. When the web browser is directed to http://IP-ADDRESS, it will automatically be redirected to http://IP-ADDRESS/sysworkflow/LANG/SKIN/login/login. If not set, then the default skin is "neoclassic".
• disable_download_documents_session_validation = 0|1
  Set to 1 to enable the download of input or output documents without restrictions. This means that is not necessary to have a valid session or the right user permissions to download the document. If set to 0, the user must have a valid session and the correct user permissions to download the input or output document. If not set, then the default value is 0. For more information, read the Input Documents Download Restriction section.
• disable_php_upload_execution = 0|1
  Set to 1 to disable the upload and execution of PHP files. By default the value is set to 0. This flag can be set for the whole ProcessMaker installation or individually for eack workspace. If the flag is active and a user tries to upload a PHP file, an alert message with "phpUpload" type will be recorded in the ProcessMaker Standard Log. This restriction includes: inputs documents, public files, documents, BPMN and classic dynaforms and files uploaded through the file and multiple file uploader control.
• enable_blacklist = 0|1
  Set to 1 to activate the Plugin/Trigger Code Security Scanner feature or to 0 to deactivate it.
• load_headers_ie = 0|1
  Set to 1 to disable compatibility mode with the ProcessMaker 2.x code and header:
  
  <meta http-equiv="X-UA-Compatible" content="IE=$VERSION_IE" />
  Otherwise, set to 0 to maintain compatibility with code and headers that are used only in ProcessMaker 2.x processes.
• memory_limit = "XM"
  

  Warning: As of ProcessMaker 3.5.0, the memory_limit setting is removed. Edit the php.ini file instead.

  Example: memory_limit = "512M"
  Set the maximum amount of memory available for each login session in ProcessMaker. Use "M" for megabytes, "K" for kilobytes and "G" for gigabytes. It is not recommended to set this value to less than "100M", which is the default. If generating large Output Documents, it may be necessary to increase this value.
• mobileNotifications = true|false
  Set to false to deactivate notifications in ProcessMaker Mobile.
  mobileNotifications = false;

  By default, mobile notifications are enabled. If this setting is not found in the env.ini file, the default value is true.

  

  As of ProcessMaker Mobile 2.x, get one notification per arrived case.

  

• redirect_to_mobile = 0|1
  Set to 1 to open the direct case link directly in the ProcessMaKer Mobile app. Set to 0, to open the link in the device's browser. The default is 0.
• session_block = 0|1
  Set to 1 to block the use of multiple browser instances of ProcessMaker. The default is 0. For more details, see blocking multiple browser instances.
• system_utc_time_zone = 0|1
  Set to 1 to enable the multi time zone. Default is 0.
  For best practices using this parameter, see Time Zone best practices.
• time_zone = "zone"
  Set the time zone of the ProcessMaker server. This setting determines the time zone used for all timestamps in ProcessMaker Community Edition, such as the starting and ending time for cases. By default, the time zone is set to "America/New_York". A list of available timezones can be found at: http://php.net/manual/en/timezones.php
• expiration_year = number_of_years
  This is the default number of years when a user account in ProcessMaker will expire, which is 1 by default. This setting can also be modified inside ProcessMaker by going to Admin > System > System Settings and changing the Default User Expiry Date (Years) field.
• wsdl_cache = 0|1
  Set to 0 to disable the caching of WSDL (Web Services Description Language) function calls. The default is 1, so WSDL function calls are cached for up to 24 hours, which increases the reliability (especially if there are connection problems), but is a problem if immediate execution for debugging is necessary.

Document Download Restriction

The disable_download_documents_session_validation flag has been implemented to allow the download of Input Documents, Output Documents and attached files by unauthorized users in version 3.1.3 and later. This is useful if needing to include links to documents in emails and Output Documents or accessing documents through web services or REST, so that the recipient isn't forced to login to ProcessMaker to access the document.

If the disable_download_documents_session_validation flag is set to 0 or is not included in the env.ini file, documents can only be downloaded by users who have a valid login session and are allowed to access the document either as the currently assigned user to a task containing the document or through process permissions to the Input Document, Ouput Document or task containing a Dynaform with a Multiple File field.

This restriction affects:

• Input Document direct links.
• Input Documents set as steps in tasks.
• Documents uploaded using the Multiple File Uploader control.
• Documents uploaded using the File control.
• URLs to documents returned by the inputDocumentList() and outputDocumentList() web services.
• Downloading files using GET /cases/{app_uid}/input-document/{app_doc_uid}/file?v={app_doc_version}
• The app_doc_link property returned by GET /cases/{app_uid}/output-document/{app_doc_uid}

Remember that this restriction is enabled by default. If the user is not allowed to download the file, a "403 Access denied" error message will be displayed:

If this setting is not enabled and the user doesn't have an open login session, then clicking on a link to download an Input or Output Document file will redirect to the ProcessMaker login screen. After login, the web browser will be redirected to the URL to download the file.

This setting is often enabled when needing to include links to files in emails and Output Documents or when accessing ProcessMaker files remotely via REST or web services. However, keep in mind that enabling this setting is a security hole, since it allows files to be downloaded using their file IDs and version numbers without verifying that the downloader is a valid ProcessMaker user and has permissions to access the file. If needing to guarantee that the files saved in ProcessMaker can only be accessed by authorized users, then do NOT enable this setting.

MySQL Logging

If the debug_sql option is set to 1 (or debug is set to 1), then every SQL query to the wf_<WORKSPACE> database (which is named wf_workflow by default) will be written in the following log file:

Each line in the log file records SQL actions in the following format:

For example, here is the shared/log/propel.log file for the admin user's login from the IP address 192.168.0.168:

Logging will noticeably slow down ProcessMaker's performance, so it is not suggested to use this option except for debugging. The log file is not automatically deleted, so it will continue to append new information until the file system runs out of space. If SQL logging is enabled for long periods of time, it is a good idea to periodically delete the log file so it doesn't occupy too much hard drive space.

Note that the processing time is in seconds and milliseconds, so a time of 1.309 means 1 second and 309 milliseconds.

Blocking Multiple Browser Instances

Set the setting session_block to 1 in the env.ini file to disallow the use of multiple browser instances of ProcessMaker. If this setting is not found in the env.ini file, the default value is 0.

This restriction affects the following tabs: Home, Designer, Dashboards, KPIs, Admin and any of the options inside them.
Whenever trying to open multiple instances, the following warning page will display:

For the restriction to take effect, it is strongly recommended to log out of ProcessMaker and clear the cache of the browser.

Note: This restriction does not affect Dynaforms or Processes in the Designer tab that are automatically opened in other tabs in Internet Explorer 11 and later.