Overview
ProcessMaker 3.2 can manage numerous workspaces at a time. Each workspace has one MySQL database for each workspace to facilitate the use of ProcessMaker in hosted servers that 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 the prefix RBAC added to their names contain 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 image below to see the Entity-Relationship diagram of this database.
Database Schema Changes From ProcessMaker 3.1.3 to 3.2
The following tables describe all the changes made to the ProcessMaker Database Schema from ProcessMaker version 3.1.3 to 3.2. These changes include new fields, updated fields, new keys and field type changes. Notice that no field has been removed, which means that existing records won't get lost when upgrading from ProcessMaker 3.1.3 to 3.2.
New Tables
APP_ASSIGN_SELF_SERVICE_VALUE_GROUP |
Updated Tables
Table | Changes |
---|---|
ABE_CONFIGURATION | New field:
|
APP_ASSIGN_SELF_SERVICE_VALUE |
New field:
|
APP_CACHE_VIEW | New Key:
|
APP_DOCUMENT | New key:
|
CASE_CONSOLIDATED | New Key:
|
DYNAFORM | New fields:
|
GMAIL_RELABELING | Updated fields:
|
OUTPUT_DOCUMENT | New fields:
|
PROCESS | New fields:
|
REPORT_TABLE | New fields:
|
TASK | New fields:
|
TRIGGERS | New fields:
|
USERS | New Fields:
|
WEB_ENTRY_EVENT | New fields:
|
Database Schema Changes From ProcessMaker 3.0 to 3.2
The following tables describe all the changes made to the ProcessMaker Database Schema from ProcessMaker version 3.0 to 3.2. These changes include new fields, updated fields, new keys and field type changes. Notice that no field has been removed, which means that existing records won't get lost when upgrading from ProcessMaker 3.0 to 3.2.
New Tables
APP_ASSIGN_SELF_SERVICE_VALUE_GROUP | NOTIFICATION_DEVICE |
APP_SEQUENCE | NOTIFICATION_QUEUE |
EMAIL_EVENT | SCRIPT_TASK |
GMAIL_RELABELING | TIMER_EVENT |
Updated Tables
Table | Changes |
---|---|
ABE_CONFIGURATION |
New Fields:
|
ADDITIONAL_TABLES |
New Keys:
|
ADDONS_MANAGER |
New Keys:
|
APPLICATION |
New Fields:
|
APP_ASSIGN_SELF_SERVICE_VALUE |
New fields:
|
APP_CACHE_VIEW |
New Keys:
|
APP_DOCUMENT |
New Fields:
|
APP_HISTORY |
New Keys:
|
BPMN_FLOW |
Updated Fields:
|
CASE_CONSOLIDATED |
New Keys:
|
CASE_SCHEDULER |
New Fields:
|
CONTENT |
New Keys:
|
DASHBOARD | Updated Fields:
|
DB_SOURCE |
Updated Fields:
|
DEPARTMENT |
New Fields:
|
DYNAFORM |
New Fields:
|
EMAIL_SERVER | Updated Fields:
|
EVENT |
New Keys:
|
GROUPWF |
New Fields:
|
INPUT_DOCUMENT |
New Fields:
|
LIST_COMPLETED |
Updated Fields:
|
LIST_INBOX |
Updated Fields:
|
LIST_PARTICIPATED_LAST |
New Fields:
|
LIST_UNASSIGNED |
Updated Fields:
|
LOGIN_LOG |
New Fields:
|
OUTPUT_DOCUMENT |
New Fields:
|
PROCESS |
New Fields:
|
PROCESS_VARIABLES |
New Fields:
|
PRO_REPORTING |
New Fields:
|
REPORT_TABLE |
New Fields:
|
SUB_APPLICATION |
New Keys:
|
TASK |
New Fields:
|
TRIGGERS |
New Fields:
|
USERS |
Updated Fields:
|
USR_REPORTING |
New Fields:
|
WEB_ENTRY_EVENT | New Fields:
|
Database Schema Changes from ProcessMaker 3.2.1 to 3.2.2
The following table describes all the changes made to the ProcessMaker 3.2.2 database schema from ProcessMaker 3.2.1. These changes include updated fields. Notice that no field has been removed, which means that existing records won't get lost when upgrading ProcessMaker.
New Tables
PLUGINS_REGISTRY |
Updated Tables
Tables | Changes |
---|---|
APPLICATION |
Updated Field:
|
APP_DOCUMENT |
New Keys:
|
APP_MESSAGE |
New Key:
|
USERS |
Updated Field:
|
APP_DELAY |
New Fields:
|
USERS_PROPERTIES |
New Field:
|
WEB_ENTRY |
Updated Fields:
|
LIST_INBOX |
Updated Fields:
|
LIST_PARTICIPATED_HISTORY |
Updated Fields:
|
LIST_PARTICIPATED_LAST |
Updated Fields:
|
LIST_COMPLETED |
Updated Fields:
|
LIST_PAUSED |
Updated Fields:
|
LIST_CANCELED |
Updated Fields:
|
LIST_MY_INBOX |
Updated Fields:
|
LIST_UNASSIGNED |
Updated Fields:
|
WEB_ENTRY_EVENT |
Updated Fields:
|
EMAIL_EVENT |
Updated Field:
|
PLUGINS_REGISTRY |
New Fields:
|
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 of 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 using 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 using 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\