

- #EXTERNAL WORKSPACE MANAGER PLUGIN UPDATE#
- #EXTERNAL WORKSPACE MANAGER PLUGIN UPGRADE#
- #EXTERNAL WORKSPACE MANAGER PLUGIN SERIES#
- #EXTERNAL WORKSPACE MANAGER PLUGIN WINDOWS#
Create a PmFunction Class for extending Processmaker : See PMFunction Class below.Create an element for the Processmaker Dashboards : See Dashlet for the Dashboard below.Create external step for Processmaker : See External Step below.The Permission 'PM_ PLUGIN-NAME' : See New Role and Permission below. Create the Role 'PROCESSMAKER_ PLUGIN-NAME' and.Create new option in the menu of cases : See New Options in the Cases Sidebar below.Create an example Page : See Example Page below.Change system logo : See System Logo below.
#EXTERNAL WORKSPACE MANAGER PLUGIN SERIES#
The new-plugin script will ask a series of Yes/No questions: Saved 2061 bytes in file deleteCases/config/ Saved 2067 bytes in file deleteCases/config/propel.ini Saved 3056 bytes in file deleteCases/config/schema.xml Saved 183 bytes in file deleteCases/messageShow.xml Saved 388 bytes in file deleteCases/setup.xml Using DSN Connection plugin directory /opt/plugins/deleteCases To create a new plugin, use the command: php gulliver new-plugin pluginNameįor example, create a plugin named "deleteCases": # cd /opt/processmaker/workflow/engine
#EXTERNAL WORKSPACE MANAGER PLUGIN UPDATE#
Update-plugin-attributes > Update the plugin attributes in all workspaces Test-functional > launch functional tests for an application Propel-insert-sql > insert sql for current model Propel-dump-data > dump data to fixtures directory Propel-build-sql > create sql for current model Propel-build-schema > create schema.xml from existing database Propel-build-model > create classes for current model

Propel-build-db > create database for current model Propel-build-crud > generate basic CRUD files for an existing class Generate-unit-test-class > generate a unit test file for an existing class Then, execute the php gulliver command to see a list of the available options.įor example: # cd /opt/processmaker/workflow/engineĬreate-poedit-file > create poedit file for system labels processmaker/workflow/engine/gulliver-win.bat Options of the gulliver ScriptĪs the root user (or a user with administrative permissions), go to the /processmaker/workflow/engine/ directory. Log in to the ProcessMaker server as the root user or a user with administrative powers. The gulliver script needs to be executed inside the workflow/engine directory. To create a plugin in Gulliver, symbolic links have to first be established in the server where ProcessMaker is installed. ProcessMaker is programmed using a custom PHP development framework named Gulliver. The use of UTF-8-BOM or other encodings may cause issues with other ProcessMaker plugins. Restrictionįiles within the custom plugins must have the UTF-8 encoding.
#EXTERNAL WORKSPACE MANAGER PLUGIN WINDOWS#
After the plugin has been created, it can be exported to other installations of ProcessMaker, including Windows servers. Plugins cannot be developed on Windows servers, because symbolic links are needed. Plugins are developed using the gulliver new-plugin command on a Linux/UNIX server. Instead, it is recommended to develop a plugin to modify the source code.
#EXTERNAL WORKSPACE MANAGER PLUGIN UPGRADE#
Version 3.0.1.8 and later offers a new plugin creation script, which is based upon the new 3.0 interface using the Ext JS framework.Īlthough the ProcessMaker core is open source, it is not recommended to edit it, because each version upgrade will overwrite any changes in the code. Plugins are used to give additional functionality to ProcessMaker and/or customize its interface and databases. Creating a cron Using ProcessMaker Classes.Applying Changes With gulliver propel-build-crud.Creating SQL Files with gulliver propel-build-sql.Creating Classes with gulliver propel-build-model.Step 4: Linking the Plugin Files into ProcessMaker.Importing Additional Files into a Plugin.
