Skip to main content

Create a Plugin in the in Linux for Processmaker 3.0

**************************************************************************
  To Create a Plugin in the in Linux for Processmaker 3.0
**************************************************************************
Now let us create the plugin using Linux/ ret hat os for the processmaker. The main Steps to Plugins can not be created on Windows servers, because Windows does not support symbolic links;

however, there is an experimental script for Windows servers available at <INSTALL-DIRECTORY>/workflow/engine/gulliver-win.bat which can be tested.
http://wiki.processmaker.com/3.0/Plugin_Development

The steps are given below as a step by step please follow this any query just post commands.



Step :1
============
root@BPMServer:~# # ln -s /opt/processmaker/gulliver/bin/gulliver /opt/processmaker/workflow/engine

********************************************************************
Step :3
============
root@BPMServer:~# cd /opt/processmaker/workflow/engine

********************************************************************
Step :3
============
root@BPMServer:/opt/processmaker/workflow/engine# php gulliver

available pake tasks:
create-poedit-file > create poedit file for system labels
args: [<lang-id> [<country-id> [verbose]]]
generate-unit-test-class > generate a unit test file for an existing class
args: <class-filename>
new-plugin > build new plugin
args: <name>
pack-plugin > pack plugin in .tar file
args: <plugin>
propel-build-crud > generate basic CRUD files for an existing class
args: <class-name> <table-name> <plugin-name>
propel-build-db > create database for current model
propel-build-model > create classes for current model
propel-build-schema > create schema.xml from existing database
propel-build-sql > create sql for current model
propel-dump-data > dump data to fixtures directory
propel-insert-sql > insert sql for current model
test-all > launch all tests
test-functional > launch functional tests for an application
test-unit > launch unit tests
update-plugin-attributes > Update the plugin attributes in all workspaces
args: <plugin-name>
version > gulliver version

********************************************************************
Step :4
============
root@BPMServer:/opt/processmaker/workflow/engine# php gulliver new-plugin sample

using DSN Connection
creating plugin directory /opt/plugins/sample
saved 385 bytes in file sample/setup.xml [pluginSetup.xml]
saved 183 bytes in file sample/messageShow.xml [pluginMessageShow.xml]
saved 3055 bytes in file sample/config/schema.xml [pluginSchema.xml]
saved 2065 bytes in file sample/config/propel.ini [pluginPropel.ini]
saved 2059 bytes in file sample/config/propel.mysql.ini [pluginPropel.mysql.ini]
Change system logo [y/N]: n
********************************************************************
Create an example Page [Y/n]: y
saved 147 bytes in file sample/menusample.php [pluginMenu]
saved 924 bytes in file sample/sampleApplication.php [pluginApplication.php]
saved 45 bytes in file sample/sampleApplication.html [pluginApplication.html]
saved 6512 bytes in file sample/sampleApplication.js [pluginApplication.js]
saved 1519 bytes in file sample/sampleApplicationAjax.php [pluginApplicationAjax.php]
********************************************************************

Create new option in the menu of cases [Y/n]: y
saved 2370 bytes in file sample/menuCasessample.php [pluginMenuCases]
saved 542 bytes in file sample/sampleApplication2.php [pluginApplication2.php]
saved 45 bytes in file sample/sampleApplication2.html [pluginApplication2.html]
saved 7595 bytes in file sample/sampleApplication2.js [pluginApplication2.js]
saved 542 bytes in file sample/sampleApplication3.php [pluginApplication3.php]
saved 45 bytes in file sample/sampleApplication3.html [pluginApplication3.html]
saved 561 bytes in file sample/sampleApplication3.js [pluginApplication3.js]
********************************************************************

Create the Role 'PROCESSMAKER_sample' and
the Permission 'PM_sample' [y/N]: y


********************************************************************
Create a Redirect Login for the Role 'PROCESSMAKER_sample' [y/N]: n

********************************************************************
Create external step for Processmaker [y/N]: n
********************************************************************
Create an element for the Processmaker Dashboards [y/N]: n
********************************************************************
Create a PmFunction Class for extending Processmaker [y/N]: y

saved 480 bytes in file sample/classes/class.pmFunctions.php [class.pmFunctions.php]

saved 1531 bytes in file sample.php [pluginMainFile]

saved 381 bytes in file sample/class.sample.php [pluginClass]
********************************************************************

Then move the folder to the path of:

\opt\processmaker\plugins

with the pluginname.php and plugin folder and refresh the plugin manager -> and make the plugin to be enabled...

Comments

Popular posts from this blog

vagrant up not working windows 10 | Stderr: VBoxManage.exe: error: Failed to get device handle and/or partition

 vagrant up not working windows 10 If you get an error message during  vagrant up  or when starting a VirtualBox machine, telling you that VT-x is not available, a reason may be that you have enabled Hyper-V on your Windows 10 machine: VirtualBox and Hyper-V cannot share the VT-x CPU: $ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Checking if box 'thesteve0/openshift-origin' is up to date... ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: hostonly ==> default: Forwarding ports... default: 8443 (guest) => 8443 (host) (adapter 1) default: 22 (guest) => 2222 (host) (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... There was an error while executing `VBoxManage`, a CLI used by Vagrant for controlling VirtualBox. The command an

Create a Plugin in the in Windows for Processmaker 3.0

**************************************************************************   To Create a Plugin in the in Windows for Processmaker ************************************************************************** Now let us create the plugin using windows os for the processmaker. The main Steps to Plugins cannot be created on Windows servers, because Windows does not support symbolic links; however, there is an experimental script for Windows servers available at <INSTALL-DIRECTORY>/workflow/engine/gulliver-win.bat which can be tested. http://wiki.processmaker.com/3.0/Plugin_Development The steps given below as a step by step please follow this any query just post commands. Step :1 ============ C:\Bitnami\processmaker-3.1-1\apps\processmaker\htdocs\workflow\engine>gulliver-win.bat new-plugin deleteCases using DSN Connection The plugin deleteCases exists in this file C:\Bitnami\processmaker-3.1-1\apps\pr ocessmaker\htdocs\workflow\engine\plugins\deleteCases\class.deleteCas

HTML to Office Word header and footer generation

Here is an HTML to Office Word header and footer generation code Below: fwrite($oFile, <html xmlns="http://www.w3.org/TR/REC-html40" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word"> <head> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"> <title> </title> <!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Print</w:View> <w:Zoom>100</w:Zoom> </w:WordDocument> </xml><![endif]--> <style> <!-- /* Style Definitions */ p.MsoHeader, li.MsoHeader, div.MsoHeader{ margin:0in; margin-top:.0001pt; mso-pagination:widow-orphan; tab-stops:center 3.0in right 6.0in; } p.MsoFooter, li.MsoFooter, div.MsoFooter{ margin:0in 0in 1in 0in; margin-bottom:.0001pt; mso-pagination:widow-orpha