ProcessMaker is a process automation platform that helps organizations optimize and scale their business operations. By combining workflow automation, AI-driven decision-making, and advanced analytics, ProcessMaker empowers businesses to streamline complex processes, improve efficiency, and enhance customer experiences.
We used BizTalk Server as we had all other integrating applications developed on .Net and using Microsoft development environment. Kafka is best if integration is between non-Microsoft applications. We had few adapters developed using Microsoft .Net framework. BizTalk is well …
Microsoft BizTalk was chosen as the integration hub many years ago. It is still in use in a number of places in the organization however we are no longer developing specifically for this product in mind. We now develop in a number of places and if Microsoft BizTalk is the …
We did look at Jitterbit dataloader from Salesforce.com. Jitterbit seems like a pretty decent solution if you are doing a lot of uploads into Salesforce.com. However, its not nearly as flexible as Microsoft Biztalk is. Biztalk allows you to create any type of custom solution …
BizTalk was selected here mainly because it is easy to integrate to a .NET application (most of them are Web Service, WCF SOAP, WCF REST and Web API) and many backend databases are Microsoft SQL Server. Another benefit is that the monitoring job is easy to set up and centralize …
We looked at all and tested some with the final recommendation being for ProcessMaker. The features the were key to our decision making were its easy integration options and capabilities, its open source version for our extended customization needs and its ease of use and web …
In the short run, ProcessMaker blows KiSSFLOW away. It is easy to understand and use. But in the long run, once you get into more complicated actions, they equal out. The price was right, and while we eventually went for another option, ProcessMaker would have been the next …
Before making the decision to get ProcessMaker, we assessed different and best options in the market, which are also quite competitive. Kissflow, Blueworks Live, and Bizagi, being the most relevant and Adonis, to mention the ones we consider the most relevant and capable of …
It is far cheaper than JIRA. I have used JIRA , the UI is good as compared to processmaker. But compared to workflow designing and management, I found processmaker far easier. And yes ProcessMaker requires less resources to run on.
Based on our experience, the agent for ProcessMaker Task Mining is more robust than for either of the competing products. However Celonis is has a significantly more mature user interface, and UiPath has a significantly more configurable interface.
It is perfectly suited if some heavy operation needs to be automated where jobs can be queued up. Scalable app which is required to develop in a lesser time frame. Good for when users should be able to change rules more frequently without any downtime, like promotions. The server is well proven in the market. BizTalk server is the best fit if all other integration adapters are developed using Microsoft applications and if all applications are meant to be processed on a Windows environment.
I loved it. You will not get an easier interface. You can develop workflow processes in a simple way, one which allows anyone to understand what you are trying to accomplish; however, you will get into some issues if your employees are scared of coding (when you get to the advanced features). For some, this will never be an issue as the knowledge you need is very basic. But for the school I was working with, it would have stopped them cold
BizTalk uses Microsoft Visual Studio as the IDE (integrated development environment) tool, and it's very easy to use.
The orchestration engine of BizTalk addresses resource issue very well for long-running business processes by dehydrating and rehydrating orchestration instances.
BizTalk is very easy to integrate if the development is mainly on the Microsoft software family.
BizTalk needs to be better at tracking down errors after the fact. Input files by default get deleted after processing successfully, unless you specifically specify that they don't. This can be an issue where you need to see what the input file contained, since you may have errors showing up in your target platform, in our case this was SAP.
BizTalk logging needs improved. It needs to be able to log the content of the messages it sends and receives. It would be good if the log had a link to the input and output files.
BizTalk needs to allow a simple way to preserve the input and output files for debugging purposes. A master setting on the orchestration would be helpful for this.
Complications when you get to the more advanced pieces. When trialing, I found that the more advanced a process got, the more complicated it got for me in coding. When you begin using the more advanced features, you will find that you need to have a basic knowledge of coding - otherwise you won't go any further. This was my sole issue. Unfortunately, it was one that would have brought the school to a grinding halt if they were to ever get more complicated than they were.
Microsoft BizTalk is not an intuitive product. It requires many hours of looking through the settings to achieve what you need. Using 3rd party DLLs is a nightmare as you are forced to register them in the GAC of the server and this process is quite cumbersome just to use a DLL.
I gave this overall rating for ProcessMaker due to its overall flexibility, design and ease of use for most. Examples of this from us include it being an excellent and trustworthy tool for automating processes, the abilities and capabilities for real-time process tracking and the web-based accessibility and implementation which allows for easy access and management of the tool.
BizTalk Server has been supported for more than 15 years. It is well proven in the market. Microsoft has provided excellent support with technical issues.
We did look at Jitterbit dataloader from Salesforce.com. Jitterbit seems like a pretty decent solution if you are doing a lot of uploads into Salesforce.com. However, its not nearly as flexible as Microsoft Biztalk is. Biztalk allows you to create any type of custom solution you wish, whereas Jitterbit is much more limited.
Based on our experience, the agent for ProcessMaker Task Mining is more robust than for either of the competing products. However Celonis is has a significantly more mature user interface, and UiPath has a significantly more configurable interface.
I gave this rating for the adaptability and growth for Processmaker for its many capabilities for support and flexibility. These include ease of integration with many other systems, its open source version for its extended customization and capabilities of the tool and its low-code / no-code capabilities to be able to easily design and automate processes with minimal or no-code.
I'm using Communication edition to introduce BPMN in my organization. I can build the first process in a short time, make my boss more confident with my job.
But, with ProcessMaker, we need more time to design code to handle the process, and without PHP/Javascript Programmer, it seems hard to work with more and more processes online.
However, IE Browser is not well supported, somewhat let the user confuse.