The other day I wrote about a list of top open source bpm / workflow solution. One of the mentioned solution is ProcessMaker.com – an open source business process management (BPM) and workflow software designed for small and mid-sized businesses (SMBs) and organizations.
I decided to give ProcessMaker a try just to check out the features and to find out if I could really automate a business process based on the community edition of ProcessMaker.
Some of my previous experience with BPM tools were Metastorm BPM as well as K2, both are proprietary and works on .NET platform.
If you ask me what’s my understanding of Business Process Management, I would say it’s all about automating business processes.
Most organizations have complex business processes which involves multiple parties to make a decision. A BPM tool will definitely assist and help to determine what and who should take an action based on a designed process map.
My ProcessMaker Review
My suggestion to those who are also planning to install ProcessMaker, if you’re not too familiar configuring and setting up the LAMP environment, try downloading the Windows Installer version instead. With this version, all you need to do is to run the setup file and there will be an installation wizard to help you set everything up. I tried this on another machine with Windows XP and ProcessMaker was installed successfully without any problems.
Once installed, I logged in. As usual, I was like, what is this for? Where should I start? etc?
This is what I did!
- Glanced through quickly the ProcessMaker Wiki
- Downloaded the Credit Card Application process and imported it to my local ProcessMaker.
- Tried creating users, processes, etc. Was having difficulty here since I didnt know what was really going on.
- Went through the ProcessMaker Demos. This was an important step as many of the questions that I had was answered through the demos. If the ProcessMaker people are reading this, I would suggest to reordering the demo’s from 1 – 7 rather than 7 – 1. 🙂
- Downloaded the Expense Report process and tweaked it further.
So the end result of my test, I managed to create my very own Claims Reimbursement Process based on tweaking the Expense Report sample. I gave it a run by logging in as the applicant to submit the claim followed by going in as the approver to approve the claim and lastly as the finance person to process the payment. All these were done and achieved in within 3 days of learning ProcessMaker.
There is still a lot for me to learn about ProcessMaker, but overall it was a good experience and I found out the following pros and cons:
Pros of ProcessMaker
- Everything from designing of the process to using the system is all web based. Need not install anything on the desktop.
- The functions and user interface are consistent thus making it easier to learn and apply.
- Lots of samples to download and learn from making it a truly open and transparent environment.
- Some moderators and users in the forum do provide help and tips for newbies. Rather than replying a short RTFM to the newbies, they would go the extra mile to explain and attempt to solve the problem.
Cons of ProcessMaker
- Since every is web based, the designing process can be a bit slower as compared to a desktop application. Also if you did a mistake like accidentally deleting something, you can’t press Ctrl + Z to undo the mistake.
- The number of active users in forum are still lacking. The knowledge base would be even better if there are more users and people asking and contributing.
Over the next few days, I will attempt to roll out the Claims Reimbursement Process to my office environment to fully test the system. From there on, I should be able to add even more pros and cons of ProcessMaker, and also share more experience. Hopefully in the long run, we can utilize ProcessMaker to the fullest to automate even more processes.