Skip to main content

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.deleteCases.php
********************************************************************
Step :2
============
Do you want to create a new plugin? [Y/n]y
creating plugin directory C:\Bitnami\processmaker-3.1-1\apps\processmaker\plugin
s\deleteCases
saved 387 bytes in file deleteCases\setup.xml [pluginSetup.xml]
saved 183 bytes in file deleteCases\messageShow.xml [pluginMessageShow.xml]
saved 3056 bytes in file deleteCases\config\schema.xml [pluginSchema.xml]
saved 2067 bytes in file deleteCases\config\propel.ini [pluginPropel.ini]
saved 2061 bytes in file deleteCases\config\propel.mysql.ini [pluginPropel.mysql
.ini]
********************************************************************
Step :3
============
Change system logo [y/N]y
saved 750 bytes in file public_html\deleteCases.png [deleteCases.png]
Create an example Page [Y/n]y
saved 151 bytes in file deleteCases\menudeleteCases.php [pluginMenu]
saved 932 bytes in file deleteCases\deleteCasesApplication.php [pluginApplicatio
n.php]
saved 45 bytes in file deleteCases\deleteCasesApplication.html [pluginApplicatio
n.html]
saved 6518 bytes in file deleteCases\deleteCasesApplication.js [pluginApplicatio
n.js]
saved 1519 bytes in file deleteCases\deleteCasesApplicationAjax.php [pluginAppli
cationAjax.php]
********************************************************************
Step :4
============
Create new option in the menu of cases [Y/n]y
saved 2384 bytes in file deleteCases\menuCasesdeleteCases.php [pluginMenuCases]
saved 547 bytes in file deleteCases\deleteCasesApplication2.php [pluginApplicati
on2.php]
saved 45 bytes in file deleteCases\deleteCasesApplication2.html [pluginApplicati
on2.html]
saved 7599 bytes in file deleteCases\deleteCasesApplication2.js [pluginApplicati
on2.js]
saved 547 bytes in file deleteCases\deleteCasesApplication3.php [pluginApplicati
on3.php]
saved 45 bytes in file deleteCases\deleteCasesApplication3.html [pluginApplicati
on3.html]
saved 565 bytes in file deleteCases\deleteCasesApplication3.js [pluginApplicatio
n3.js]
********************************************************************
Step :5
============
Create the Role 'PROCESSMAKER_DELETECASES' and
the Permission 'PM_DELETECASES' [y/N]y
********************************************************************
Step :6
============ Create a Redirect Login for the Role 'PROCESSMAKER_DELETECASES' [y/N]y
********************************************************************
Step :7
============
Create external step for Processmaker [y/N]y
saved 1042 bytes in file deleteCases\stepdeleteCasesApplication.php [pluginStepA
pplication.php]
saved 45 bytes in file deleteCases\stepdeleteCasesApplication.html [pluginStepAp
plication.html]
saved 2707 bytes in file deleteCases\stepdeleteCasesApplication.js [pluginStepAp
plication.js]
saved 740 bytes in file deleteCases\stepdeleteCasesApplicationAjax.php [pluginSt
epApplicationAjax.php]
********************************************************************
Step :8
============
Create an element for the Processmaker Dashboards [y/N]y
saved 3702 bytes in file deleteCases\classes\class.dashletdeleteCases.php [plugi
nDashletClass.php]
saved 1788 bytes in file pluginDashlet.html
********************************************************************
Step :9
============
Create a PmFunction Class for extending Processmaker [y/N]y
saved 484 bytes in file deleteCases\classes\class.pmFunctions.php [class.pmFunct
ions.php]
saved 3089 bytes in file deleteCases.php [pluginMainFile]
saved 384 bytes in file deleteCases\class.deleteCases.php [pluginClass]
********************************************************************
Step :10
============
Press any key to continue . . .
Then move the folder to the path of:
C:\Bitnami\processmaker-3.1-1\apps\processmaker\htdocs\workflow\engine\plugins
with the pluginname.php and plugin folder and refresh the plugin manager -> and make the plugin to be enabled...

Download the sample plugin:
Click to download

Comments

  1. Hello, Thanks for your valuable post
    In the first step, you mentioned that using DSN connection.
    I would be appreciated if you could explain that in more details
    Best Regards

    ReplyDelete
    Replies
    1. Hi,

      Yes windows cannot create the plugin and create the symbolic links. I prefer the Linux for creating plugins. You can test the plugin in windows via /workflow/engine/gulliver-win.bat. You can trigger this file in schduler and can test the plugin

      Delete

Post a Comment

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

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