Boomi vs. Okta Workflows

Dell Boomi is well-suited as a middleware to talk between systems. I am a personal fan of Dell's products and I enjoy this service. Dell Boomi is very easy to use, even to the less technically-inclined user. It is less appropriate to use in one system alone, but users would still find it functional in one system alone because it helps manage the system's metadata and allows that system to be integrated with other systems in the future.

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

• Pre-built connectors to almost anything which greatly reduce time to release of your integration needs.
• Easy to use development platform with drag&drop features. Non-technical people could build simple integration processes in no time.
• Great user community where you can get quick help if needed. Boomi people hang around there a lot.

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

• More from a development perspective. It is always difficult to use the properties features. It takes a while to understand how the data/variables can be used across an integration.
• Dell Boomi should also invest more on API Management and not just seen as a ETL,ESB tool.
• Should roll out features more often based on users reviews.

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

Dell Boomi has provided us with the ability to connect our campus together using our various existing platforms. There are many supported features and have yet to run into something that we cannot do. Its user interface is very intuitive which would allow users to begin developing fairly easily. There is a myriad of resources available

Incentivized

First of all, as a service (cloud service), we don't need to care about server maintenance any more, no worries about incorrect configurations, about down time. Second, for maintaining, we don't need a large team to do it. And of course, using Dell Boomi instead of manual transaction could help us to avoid people mistake while inputting data or doing transactions.

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

I would rate Dell Boomi as highly performant. We have used it for 4+ years and have not had any major issues with availability or speed. We also have not observed performance degradation when connecting it with other software solutions.

Incentivized

Boomi support was responsive and knowledgable, however being a closed cloud service, it doesn't have good community support. We found the learning curve to be steep and there aren't avenues like google, forums, or blogs that provide community driven insight into the product or how to go about designing solutions using the tool

Incentivized

MuleSoft and Boomi are built on totally different frameworks. Mulesoft is an API-led network whereas Boomi is an ETL middleware approach. In easy words, Mulesoft can connect to several apps and business units, can create and reuse multiple components. Boomi offers only on-premise and on-cloud integration solutions whereas MuleSoft is capable of providing on-premise, on-cloud as well as hybrid solutions. We can say that MuleSoft is much more flexible and offers multiple integration solutions.

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

• ROI was flat. Coding directly in apps we were knowledgable in would have been faster, but maintenance higher.
• It brought good process to the integration team that was new, however I wouldn't say it was a huge gain monetarily. It is a valid path out of many paths for integration, but doesn't rule them all.

Incentivized

• 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