Camunda vs. Okta Workflows

Camunda Platform is well suited for scenarios where there are different stages in a business flow and the flow is driven by user action at each stage. For example placing of an order on an ecommerce platform. Depending on whether user was able to make the payment or not the workflow would go to dispatch or retry stage. Now the retry stage would trigger further actions like sending follow up emails etc. Likewise, dispatch stage would have a different set of actions. Since every order is important and we need to know where it stands, using Camunda Platform is imperative. Camunda Platform might not be a right choice where just a one off thing needs to be done. For example, uploading of product information by user or periodic processing of heavy images by a worker. These are all either one step processes or periodic automated processes where we can track the status without using a business modeler like Camunda Platform.

Incentivized

The integration I used Azuqua for was based on Salesforce, Wrike and Office 365. I found the integration of Salesforce reasonably straightforward, Wrike was limited in the "cards" capability but functional (there are bugs but there are also workarounds but they required assistance from the Azuqua support team) and Office 365 was quite immature (primarily around Excel bugs but also email was limited).

Incentivized

• Task orchestration
• Freeware
• Graphical interface allows normal users to understand business process model diagrams more intuitively

Incentivized

• The best part about Azuqua is that you do not need to write code. You do however need to have an understanding of logic and how the software works. This happens to fit me perfectly as someone with basic programming experience.
• Their Support is second to none. Not only are they extremely quick and responsive, but their answers are never canned responses and always provide valuable content.
• They seem to take feedback seriously and will continue to evolve and make a better product.

Incentivized

• Documentation - It is usually daunting for beginners because of lack of good documentation
• Simplified setup on local machine for Camunda Server would help developers test changes quickly
• Easier migration from one deployment version of a Camunda process to another deployment version would help in making changes and deploying them faster.
• Heap memory management becomes issue at times resulting in stuck processes. This needs to be resolved.

Incentivized

• I think it requires an easy way to migrate flows created from one user to then move the ownership to another user. It happened to us that one of our engineers left the company and he had the Azuqua account and flows. It required quite some time, cases and telephone calls to do the migration to my account.

Incentivized

The system is working as it should, keeping our programs safe from outside hackers. Helping us keep our passwords safe, convenient and already ready to get us logged into the program securely and quickly. Verification that only authorized users are able to access our company's programs. Okta Workflows (Azuqua) is a very good system that has helped our company greatly.

Incentivized

Camunda provides pretty standard product support offerings.

I evaluated Zapier and Microsoft Flow before coming across Azuqua. Zapier was too simplistic and didn't allow for transfer of enough variables. The price point also didn't work for the value it could provide. Microsoft Flow couldn't make the connection with Smartsheet, and I was unable to get Microsoft support or Smartsheet support to assist me with the issue.

Incentivized

• We've built a good business around developing and deploying Camunda for our clients over the last 7 years.
• Our clients are finding it a cost-effective way to try before they buy.
• There's an over-reliance on big offshore outsourcing shops, which hurts ROI and success rates.

• Increased time savings. We could not function as a matter of daily business if we did not have a tool to automate project folders (and complementary workflow management profiles) for the thousands of projects that flow through daily.
• Opens up a greater understanding of all the silos and divisions within the company infrastructure and tests secure means to link those groups safely and share information.
• Opens up the chance to communicate with other API information sources if our company is doing a partnership with another organization. Granted everything is square with IT security.

Incentivized