Overview
ProcessMaker can manage numerous workspaces at a time. Each workspace has one MySQL database for each workspace in order to facilitate the use of ProcessMaker in hosted servers which limit the number of databases.
Note: If upgraded from a previous version, ProcessMaker 2.8 and later will continue to use 3 databases. For more information, please check out 2.0 ProcessMaker Database Model.
wf_<workspace-name>
This database contains all the information required by the Process Engine, including information about processes, cases, users, PM Tables, etc.
Tables with prefix RBAC added to their table names contain the information about users to maintain a Role-Based Access Control (RBAC) system in ProcessMaker.
- RBAC_AUTHENTICATION_SOURCE, RBAC_PERMISSIONS, RBAC_ROLES, RBAC_ROLES_PERMISSIONS, RBAC_SYSTEMS, RBAC_USERS, RBAC_USERS_ROLES
The database also includes Report Tables designed to allow external applications to access data from ProcessMaker cases. Report Tables have the prefix PMT_ in their names. Each Report Table creates a separate table in this database, which external databases can query.
Click the images below to see the Entity-Relationship diagram of this database. The diagram is divided in three parts for better understanding.
Database Schema Changes From ProcessMaker 3.0 to 3.1
The following tables describe all the changes that ProcessMaker database schema has suffered since ProcessMaker version 3.0 to 3.1. This changes involve: "New fields added", "Fields Updated", "Default updates" and "Field Type changes". Notice there has not been removal of fields which means that existing records won't get lost when performing an upgrade from ProcessMaker 3.0 to 3.1.
New Tables Created
APP_SEQUENCE | NOTIFICATION_QUEUE |
EMAIL_EVENT | SCRIPT_TASK |
GMAIL_RELABELING | TIMER_EVENT |
NOTIFICATION_DEVICE |
Tables Updated
Table | Changes |
---|---|
ABE_CONFIGURATION | New Fields:
|
ABE_RESPONSES | Removed Keys:
|
ADDITIONAL_TABLES | New Keys:
|
ADDONS_MANAGER | New Keys:
|
APPLICATION | New fields:
|
APP_ASSIGN_SELF_SERVICE_VALUE | Updated Fields:
|
APP_CACHE_VIEW | New Keys:
|
APP_DOCUMENT | New Fields:
|
APP_MESSAGE | Required removed:
|
BPMN_FLOW | Updated Fields:
|
CASE_SCHEDULER | New Fields:
|
CONTENT | New Keys:
|
DB_SOURCE | Updated Fields:
|
DEPARTMENT | New Fields:
|
DYNAFORM | New Fields:
|
EMAIL_SERVERS | Updated Fields:
|
EVENT | New Keys:
|
GROUPWF | Default Removed:
|
INPUT_DOCUMENT | New Fields:
|
LIST_CANCELED | Updated Fields:
|
LIST_COMPLETED | Updated Fields:
|
LIST_INBOX | Updated Fields:
|
LIST_PARTICIPATED_LAST | New Fields:
|
LIST_UNASSIGNED | Updated Fields:
|
LOGIN_LOG | New Fields:
|
PROCESS | New Fields:
|
PROCES_VARIABLES | New Fields:
|
PRO_REPORTING | New Fields:
|
REPORT_TABLE | New Keys:
|
SUB_APPLICATION | New keys:
|
TASK | New Fields:
|
USERS | New Fields:
|
USR_REPORTING | New Fields:
|
Database Schema Changes From ProcessMaker 2.8 to 3.1
The following tables describe all the changes that ProcessMaker database schema has suffered since ProcessMaker version 2.8 to 3.1. This changes involve: "New fields added", "Fields Updated", "Default updates" and "Field Type changes". Notice there has not been removal of fields which means that existing records won't get lost when performing an upgrade from ProcessMaker 2.8 to 3.1.
3.1.New Tables Created
ABE_CONFIGURATION | DASHBOARD_DAS_IND | LIST_PARTICIPATED_HISTORY | MESSAGE_TYPE_VARIABLE |
ABE_REQUESTS | ELEMENT_TASK_RELATION | LIST_PARTICIPATED_LAST | NOTIFICATION_DEVICE |
ABE_RESPONSES | EMAIL_EVENT | LIST_PAUSED | NOTIFICATION_QUEUE |
APP_ASSIGN_SELF_SERVICE_VALUE | EMAIL_SERVER | LIST_UNASSIGNED | PRO_REPORTING |
APP_SEQUENCE | GMAIL_RELABELING | LIST_UNASSIGNED_GROUP | SCRIPT_TASK |
CASE_CONSOLIDATED | LIST_CANCELED | MESSAGE_APPLICATION | TIMER_EVENT |
CATALOG | LIST_COMPLETED | MESSAGE_EVENT_DEFINITION | USR_REPORTING |
DASHBOARD | LIST_INBOX | MESSAGE_EVENT_RELATION | WEB_ENTRY_EVENT |
DASHBOARD_INDICATOR | LIST_MY_INBOX | MESSAGE_TYPE |
Tables Updated
Table | Changes |
---|---|
ADDITIONAL_TABLES | Key Added:
|
APPLICATION | New Fields:
|
APP_CACHE_VIEW | New Fields:
|
APP_DELEGATION | New Fields:
|
APP_DOCUMENT | New Fields:
|
APP_HISTORY | New Fields:
|
APP_MESSAGE | New Fields:
|
APP_TIMEOUT_ACTION_EXECUTED | Default chartset updated: ENGINE=InnoDB ; |
BPMN_FLOW |
New Fields:
|
BPMN_LANE | Foreign Key added:
|
BPMN_PROJECT | Fields Updated:
|
CASE_SCHEDULER | Fields Added:
|
CONTENT | New Fields:
|
DB_SOURCE | Size Incremented:
|
DEPARTMENT | New Fields:
|
DYNAFORM | New Fields:
|
FIELDS | Fields modified:
|
GROUPWF | New Fields:
|
INPUT_DOCUMENT | New Fields:
|
LICENSE_MANAGER | Fields Updated:
|
LOGIN_LOG | New Fields:
|
PROCESS | New Fields:
|
PROCESS_VARIABLES | New Fields:
|
REPORT_TABLE | Keys Added:
|
ROUTE | New Fields:
|
TASK | New Fields:
|
SUB_APPLICATION | Key Added:
|
USERS | New Fields:
|
Database Schema changes from ProcessMaker 2.5.2 to 3.1
The following tables describe all the changes that ProcessMaker database schema suffered since the ProcessMaker version 2.5.2 to 3.1.
New Tables Created
ABE_CONFIGURATION | BPMN_FLOW | LICENSE_MANAGER | NOTIFICATION_QUEUE |
ABE_REQUESTS | BPMN_GATEWAY | LIST_CANCELED | OAUTH_ACCESS_TOKENS |
ABE_RESPONSES | BPMN_LANE | LIST_COMPLETED | OAUTH_AUTHORIZATION_CODES |
ADDONS_MANAGER | BPMN_LANESET | LIST_INBOX | OAUTH_CLIENTS |
ADDONS_STORE | BPMN_PARTICIPANT | LIST_MY_INBOX | OAUTH_REFRESH_TOKENS |
APP_ASSIGN_SELF_SERVICE_VALUE | BPMN_PROJECT | LIST_PARTICIPATED_HISTORY | OAUTH_SCOPES |
APP_SEQUENCE | BPMN_PROCESS | LIST_PARTICIPATED_LAST | PMOAUTH_USER_ACCESS_TOKENS |
APP_TIMEOUT_ACTION_EXECUTED | CASE_CONSOLIDATED | LIST_PAUSED | PRO_REPORTING |
BPMN_ACTIVITY | CATALOG | LIST_UNASSIGNED | PROCESS_FILES |
BPMN_ARTIFACT | DASHBOARD | LIST_UNASSIGNED_GROUP | PROCESS_VARIABLES |
BPMN_BOUND | DASHBOARD_INDICATOR | MESSAGE_APPLICATION | SCRIPT_TASK |
BPMN_DATA | DASHBOARD_DAS_IND | MESSAGE_EVENT_DEFINITION | SESSION_STORAGE |
BPMN_DIAGRAM | ELEMENT_TASK_RELATION | MESSAGE_EVENT_RELATION | TIMER_EVENT |
BPMN_DOCUMENTATION | EMAIL_EVENT | MESSAGE_TYPE | USR_REPORTING |
BPMN_EVENT | EMAIL_SERVER | MESSAGE_TYPE_VARIABLE | WEB_ENTRY |
BPMN_EXTENSION | GMAIL_RELABELING | NOTIFICATION_DEVICE | WEB_ENTRY_EVENT |
Tables Updated
Table | Changes |
---|---|
ADDITIONAL_TABLES | New Key:
|
APPLICATION | New fields:
|
APP_DELEGATION | New Fields:
|
APP_DOCUMENT | New Fields:
|
APP_MESSAGE | New Fields:
|
APP_DELAY | New Fields:
|
APP_CACHE_VIEW | New Fields:
|
APP_HISTORY | New Fields:
|
CASE_SCHEDULER | New Fields:
|
CONTENT | New Keys:
|
DEPARTMENT | New Fields:
|
DYNAFORM | New Fields:
|
FIELDS | New Fields:
|
GROUPWF | New Fields:
|
INPUT_DOCUMENT | New Fields:
|
LOGIN_LOG | New Fields:
|
OUTPUT_DOCUMENT | New Fields:
|
PROCESS | New Fields:
|
REPORT_TABLE | New Keys:
|
ROUTE | New Fields:
|
SUB_APPLICATION | New Keys:
|
More Information
The default workspace created in ProcessMaker is called workflow, so its database is named wf_workflow. If doing a manual installation of ProcessMaker, the setup screen provides an option to rename this database. See Consulting the ProcessMaker databases for more information about how to access this database with MySQL and phpMyAdmin.
The files for the MySQL databases are generally stored in the following locations:
Linux/UNIX:
The location depends upon your distribution, but it is generally:
- /var/lib/mysql/<DATABASE-NAME>/
For example:
- /var/lib/mysql/wf_workflow/
Windows:
If installed with the ProcessMaker Windows Installer, the MySQL files are generally stored at:
<INSTALL-DIRECTORY>\MySQL\data\<DATABASE-NAME>\
For example:
- C:\Program Files\ProcessMaker\MySQL\data\wf_workflow\
If installed with the manual installation, the MySQL files are generally stored at:
<INSTALL-DIRECTORY>\MySQL\data\<DATABASE-NAME>\
For example:
- C:\ProgramData\MySQL\MySQL Server 5.1\data\wf_workflow\