Please rate how useful you found this document: 
No votes yet

Overview

ProcessMaker 3.3.0 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.

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.2.3 to 3.3.0

The following tables describe all the changes made to the ProcessMaker Database Schema from ProcessMaker version 3.2.3 to 3.3.0. These changes include new tables and 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.2.3 to 3.3.0.

New Table

Table Fields
APP_DATA_CHANGE_LOG
  • `CHANGE_LOG_ID` int(11), NOT NULL, PRIMARY KEY, default NULL, auto_increment
  • `DATE` datetime, NULL, default NULL
  • `APP_NUMBER` int(11), NULL, default '0'
  • `DEL_INDEX` int(11), NULL, default '0'
  • `PRO_ID` int(11), NULL, default '0'
  • `TAS_ID` int(11), NULL, default '0'
  • `USR_ID` int(11), NULL, default '0'
  • `OBJECT_TYPE` int(11), NULL, default '0'
  • `OBJECT_ID` int(11), NULL, default '0'
  • `OBJECT_UID` varchar(32), NULL default ''
  • `EXECUTED_AT` int(11), NULL, default '0'
  • `SOURCE_ID` int(11), NULL, default '0'
  • `DATA` mediumtext, NOT NULL, default 'NULL'
  • `SKIN` varchar(32), NULL, default ''
  • `LANGUAGE` varchar(32), NULL, default ''
  • `ROW_MIGRATION` int(11), NULL, default '0'

Updated Tables

Table Changes
ADDONS_MANAGER Updated field:
  • ADDON_STATE varchar(255) NOT NULL DEFAULT ''
APP_ASSIGN_SELF_SERVICE_VALUE New fields:
  • `APP_NUMBER` int(11), NULL, default '0'
  • `TAS_ID` int(11), NULL, default '0'
APP_ASSIGN_SELF_SERVICE_VALUE_GROUP New fields:
  • `ASSIGNEE_ID` int(11) DEFAULT '0'
  • `ASSIGNEE_TYPE` int(11) NOT NULL DEFAULT '0'
APP_MESSAGE New fields:
  • APP_MSG_TYPE_ID tinyint(4) DEFAULT '0'
  • APP_MSG_STATUS_ID tinyint(4) DEFAULT '0'
  • PRO_ID int(11) DEFAULT '0'
DYNAFORM New fields:
  • DYN_ID int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2
GROUPWF New fields:
  • GRP_ID int(11) NOT NULL AUTO_INCREMENT
GROUP_USER New fields:
  • GRP_ID int(11) DEFAULT '0'
INPUT_DOCUMENT New fields:
  • INP_DOC_ID int(11) NOT NULL AUTO_INCREMENT
LOGIN_LOG Updated fields:
  • LOG_ID int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=6
LIST_CANCELED Updated field:
  • `DEL_INDEX` int(11), NOT NULL, PRIMARY KEY, default '0'
OBJECT_PERMISSION Updated field:
  • `OP_OBJ_TYPE` VARCHAR(20), default '', NOT NULL
OUTPUT_DOCUMENT New fields:
  • OUT_DOC_ID int(11) NOT NULL AUTO_INCREMENT
PROCESS Updated field:
  • PRO_ID int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2
TASK Updated field:
  • TAS_ID int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5
USERS Updated field:
  • USR_ID int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3

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\