Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
A great iPaaS with enormous potential
What do you like best about the product?
There are many good things about Dell Boomi that I have come to like and use in everyday work, the overall capabilities together with continuous improvements from the R&D team creates a product that you feel is not satisfying itself with its current status but always trying to adhere to customer needs and suggestion. To mention a few of the parts I like the most I would point out the following:
Environment management between Test and Production, or whatever other steps in between, is made very easy through Boomi and this makes the overall development and maintenance a pure delight once you have this setup to cover your needs.
The Scripting functionalities, both inside a process and inside a Map function, give you a very extensive set of new ways to solve a complex business case for a Customer. Covering both JavaScript and Groovy this is a very powerful addition which makes the development easy even in tough use cases.
API management and the overall capabilities for creating and maintaining Web Services, it is very easy to setup and utilize as part of your integration.
Last but not least, Boomi is doing more and more updates to increase the usability and the user experience which I find very interesting and good. There is almost always some improvements regarding UI etc. in new releases and they manage to do this without making it difficult for us, the users, to keep up and adapting to the new look and feel.
Environment management between Test and Production, or whatever other steps in between, is made very easy through Boomi and this makes the overall development and maintenance a pure delight once you have this setup to cover your needs.
The Scripting functionalities, both inside a process and inside a Map function, give you a very extensive set of new ways to solve a complex business case for a Customer. Covering both JavaScript and Groovy this is a very powerful addition which makes the development easy even in tough use cases.
API management and the overall capabilities for creating and maintaining Web Services, it is very easy to setup and utilize as part of your integration.
Last but not least, Boomi is doing more and more updates to increase the usability and the user experience which I find very interesting and good. There is almost always some improvements regarding UI etc. in new releases and they manage to do this without making it difficult for us, the users, to keep up and adapting to the new look and feel.
What do you dislike about the product?
There are small areas where I really hope that they make some improvements:
When it comes to custom scripting utilizing JavaScript or Groovy it would be very good to have syntax highlighting or similar regular features to simplify the development and minimize the risk of syntax issues.
The very good SOAP Connector, which is used for all connections using the SOAP framework, does not support NTLM/Kerberos authentication, which leaves you with the only option (if your use case cannot use oData) to develop a branded connector.
Overall the documentation is ok, and their new Community is very good, but I would like some more concrete examples in their regular documentation. Very often I read documentation about a Connector or some other shape and the bare minimal is available; sometimes a checkbox is explained by re-typing its label, which is quite annoying if you are looking for a deeper explanation of the impact of actually checking this checkbox.
When it comes to custom scripting utilizing JavaScript or Groovy it would be very good to have syntax highlighting or similar regular features to simplify the development and minimize the risk of syntax issues.
The very good SOAP Connector, which is used for all connections using the SOAP framework, does not support NTLM/Kerberos authentication, which leaves you with the only option (if your use case cannot use oData) to develop a branded connector.
Overall the documentation is ok, and their new Community is very good, but I would like some more concrete examples in their regular documentation. Very often I read documentation about a Connector or some other shape and the bare minimal is available; sometimes a checkbox is explained by re-typing its label, which is quite annoying if you are looking for a deeper explanation of the impact of actually checking this checkbox.
What problems is the product solving and how is that benefiting you?
Integration to multiple systems including Salesforce, Microsoft Dynamics Navision and third party vendors.
Developing and maintaining API and web services is a key aspect that is necessary for our implementation, this together with integration towards Salesforce for not only custom built web services but also standard operations such as Querying, Insert/Upsert/Update/Merge/Delete is vital for the success to be achieved.
Ability to streamline the integration and having a cloud based solution
Developing and maintaining API and web services is a key aspect that is necessary for our implementation, this together with integration towards Salesforce for not only custom built web services but also standard operations such as Querying, Insert/Upsert/Update/Merge/Delete is vital for the success to be achieved.
Ability to streamline the integration and having a cloud based solution
Recommendations to others considering the product:
Read up on licensing and how you best maintain and handle your connections in regard to the contract that you sign with Boomi. This is not a cheap product but well worth it if implemented and maintained in the correct and suggested way.
Take time to analyze and plan your integration before starting the development, know what you should do and have a clear idea of how you will do it before is very good to not get lost with the many ways that a process can be developed to meet a certain business case. From my experience with Boomi it is not so much the question “Can this be done?” that is the important one, but rather “How can we best do this?”.
Take time to analyze and plan your integration before starting the development, know what you should do and have a clear idea of how you will do it before is very good to not get lost with the many ways that a process can be developed to meet a certain business case. From my experience with Boomi it is not so much the question “Can this be done?” that is the important one, but rather “How can we best do this?”.
- Leave a Comment |
- Mark review as helpful
A powerful platform and tool for any integration
What do you like best about the product?
I like that Boomi is working hard to improve aspects of the UI. This is a highly important task in my opinion, since the platform and development tool is cloud and browser based. Boomi is demonstrating that this is a high priority for them, and I am enjoying the UI improvements so far.
I also like that a process can be extended with custom scripting if the built-in functionality is unable to suffice.
My favorite part about Boomi is the ability to create RESTful web services. It is intuitive to develop them, and they are very effective.
I also like that a process can be extended with custom scripting if the built-in functionality is unable to suffice.
My favorite part about Boomi is the ability to create RESTful web services. It is intuitive to develop them, and they are very effective.
What do you dislike about the product?
To keep on point with the UI improvements, there are certainly a lot of mouse clicks involved when it comes to browsing for components and configuring shapes. However, some of this has already been addressed so it is obvious that there is a backlog for improvements with the Boomi Dev team.
I also don't like the fact that a Map can't be unit tested by itself. If there was a way to unit test a map on its own (by configuring the inputs or uploading a csv that contains inputs, for example. And a way to check the expected output of each.) I believe development would be 10x more effective and more defects would be caught before production.
I do not like that a new profile is generated every time a Salesforce operation is created. I would like the option to browse for a profile before one may be created.
I also don't like the fact that a Map can't be unit tested by itself. If there was a way to unit test a map on its own (by configuring the inputs or uploading a csv that contains inputs, for example. And a way to check the expected output of each.) I believe development would be 10x more effective and more defects would be caught before production.
I do not like that a new profile is generated every time a Salesforce operation is created. I would like the option to browse for a profile before one may be created.
What problems is the product solving and how is that benefiting you?
I work on a team that integrates with Workday, Salesforce, Jive and Coupa quite a bit. Most of the Workday integrations consist of generating a flat file of some sort ( which Boomi is extremely effective with). Otherwise, integrations with Jive and Salesforce utilize their robust and effective web services.
The benefits of course with the Salesforce connector are the ability to use their web services without really coding at all. The query operations are easy to use (most of the time) and the update/create, etc. operations are even easier.
The benefits of course with the Salesforce connector are the ability to use their web services without really coding at all. The query operations are easy to use (most of the time) and the update/create, etc. operations are even easier.
Recommendations to others considering the product:
Although I would always recommend exploring your options, keep in mind that Boomi and the Atomsphere development tool is entirely in the cloud. That is tough to beat in my opinion.
Heading in the right direction
What do you like best about the product?
Capable of complex data transformations and is capable of a wide berth of use cases. Support can be very helpful and responsive. There have been several instances where we've had mission critical breakdowns and support has been awesome in putting in the hours until we got it figured out.
Their Revision History is great, especially when you're first learning the platform or want extreme version control. There's a lot of little places where you can do some major damage and having great version control mitigates development time. It's not listed as a connector, but it will work with Microsoft Dynamics Great Plains 2015 and eConnect 2014 which was nice (they do need to update the documentation for this connection though).
We had a mission critical integration that used a scripting component to sort data that would break every time there was a major update. Eventually, Boomi gave us a resource to help re-engineer the process so that it worked more in line with their development road map. This went a long way in fostering good will.
Their Revision History is great, especially when you're first learning the platform or want extreme version control. There's a lot of little places where you can do some major damage and having great version control mitigates development time. It's not listed as a connector, but it will work with Microsoft Dynamics Great Plains 2015 and eConnect 2014 which was nice (they do need to update the documentation for this connection though).
We had a mission critical integration that used a scripting component to sort data that would break every time there was a major update. Eventually, Boomi gave us a resource to help re-engineer the process so that it worked more in line with their development road map. This went a long way in fostering good will.
What do you dislike about the product?
Sometimes seemingly simple needs turn out to be very complex problems, eg sorting line item detail records on the header master record. Editing and creating custom XML profiles can be tricky, fortunately the Revision History component is fantastic. Connector management could be better, the same connector with a different ID won't deploy if you're at your cap, a problem which happens more often than you would imagine due to the strange and dangerous ways you copy processes and components. Getting at the root cause of an issue is often like peeling an onion.
What problems is the product solving and how is that benefiting you?
The primary intent of getting on the Boomi platform was to create a bi-directional sync between our Salesforce org and our instance of Great Plains which runs on a dedicated hosted server. With the some of the automation we've been able to realize using Boomi and various other applications has been profound, but when platform stability threatens that it can be harmful to our organization.
Recommendations to others considering the product:
Consider it carefully. If you're a small shop it can easily become your biggest administrative burden, but it can save your organization time with it's enterprise connections.
showing 391 - 393