Bizagi Reviews

We have migrated to the cloud, but there are a lot of issues while integrating with the cloud. There are a lot of things to improve with the cloud and reporting. We were previously working with on-premise solutions, and we had access to a lot of things, but with the cloud, they changed a lot of functionalities. Some of the things we know, but with some of the things, we are having difficulties. They have been working with apps. They have been launching new apps and widgets, but there are a lot of bugs in new functionalities, new widgets, and even new versions. That's an area where they need to improve.

In business process mapping, you have pools and dark pools. I don't see that Bizagi differentiates between a regular pool and a dark pool. Another area for improvement would be printing. It's just a small nuance to me, but if I've drawn a process that would fit on an 11 by 17 ledger page, but I really want it on a letter-size page, it doesn't show me how to shrink it down. Even if I say, "Go down to one page," it still shows me that I've got two pages. I don't know if it's a bug or if I might need more training. Where I worked before I could plot things. Now, I can only work with ledger, as large as eight and a half by 14. Sometimes, when you draw a business process, it doesn't really fit on a legal or letter-size page. But it should at least allow me to shrink it enough to fit on a letter-size page. If they had a little bit more training on printing and presentation, that would be good.

The ability to write our own code inside each activity is beneficial. Sometimes we need to create functionality that doesn't come out of the box, and this allows us to do that. The orchestration capabilities provided by the solution are good; they're helpful and fully functional, plus Bizagi has a management consultant to assist. However, they could be better, and there is significant room for improvement. We can adapt processes we created with Bizagi as our business grows and more processes become automated. We have been doing that on a live process, and it works very well. If the change we are implementing is very different to a traditional workflow, we can create a new version and design cases in the new version instead of the older one. We can modify processes already in place if the change isn't too disruptive, or we can keep using the same platform but create cases in a new workflow instead of the old one, so there's a lot of flexibility. Adapting processes is straightforward, though it depends somewhat on the complexity of the process. Making minor modifications is not complicated; we go into the studio, change the piece of code, workflow, or data model we need, and then redeploy.