Boomi

SAP Odata Integration

OpenAPI Standards

Connect to SAP S/4 Hana

Streamline Error Responses

Live Two-Way binding of Data

Better Documentation particularly in SAP segment

Application Integration

Data Synchronization

APIs

Drag and Drop Intuitive Workflow Designer

Connecting to various Enterprise Platforms such as NetSuite, SAP, MS Dynamics, Shopify

Elastic Scaling

Microservices-based Architecture

Monitoring & observability

High throughput scenarios

Hybrid Integration for both on-premise and cloud systems

Low code to no code setup

Various Endpoints

Cost effiency

Integration to communication tools such as Viber/WhatsApp/Messenger etc

API Management & Development

BPM Flow which is used to design the process

API Management

Boomi Atom sphere which handles cloud admins. This feature I didn't saw in other technology.

Process management needs to improve. Actually, it is taking more steps to open and check the instance.

Need to improve the User manual to understand core things w.r.t developer

Need to improve the free license to increase the number of external connections while learning the Dell Boomi

Quick releases.

Built-In integrations.

Doesn't require resources to be very technical.

Achieving some complex scenarios always gets tricky.

Working with APIs is an issue.

Easy integration

Supportive and patient customer service.

Perfectly priced for mid-sized companies.

New connectors added constantly.

UI not very attractive.

Somewhat limited dashboard.

Performance drop-downs once a while.

Dell Boomi is very easy to use

Dell Boomi is very easy to set up

Dell Boomi is cost-effective

Dell Boomi is an excellent service offered by an excellent company

A new, improved UI for Dell Boomi would be a nice-to-have

A user management place for Dell Boomi would be a nice-to-have

Integration with other systems such as CRM systems would be a nice-to-have

One of the best middleware which has a low code platform

Time savings compared to coding

Most important thing it has is drag and drop functionality which has quite fan base.

Easy to learn and become a developer.

I suggest is that for enterprise edition they can give the license upto to 20 default.

In test and production both they can give the same license count for enterprise by default.

They can add the excel file format to use.

Easy to build a basic integration. Less time taken to develop an integration.

Lesser learning curve. Good training materials available.

Very powerful shapes like map which can do thousands of field mapping with a click of a button.

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.

Out of the box integration with Netsuite

Cloud deployment

Work flow design of integration activity, simplifying coding required

Making sense of success, failures, and processing

Hard to scale parallel processing

It's easy to paint yourself in a corner by designing poorly performing integrations

Easy to set up.

Works with cloud or on-premise solutions.

Works with a large suite of applications.

Reliable and performs well.

Security is just OK.

The cost could be lower.

Data transformation.

Re-trying of transactions.

Logging of transactions.

EDI mapping is not as simple as other software for EDI mapping.

Would benefit from the ability to track and see deployed and schedules processes.

Support services can be cumbersome and slow to respond.

Connect to different technologies and applications using built-in connectors from Boomi.

Enable very fast delivery/development/deployment.

Very flexible -- allows you to add functionality easily (with Groovy script for example).

The community is great.

I think that at the moment we miss File listener connector and Database listener connector (we get events from FS or DB).

Drag and drop user interface. No programming language experience required.

It's all in the cloud. No maintenance effort needed except if using local atoms.

Pre-implemented connectors support a number of cloud services.

Big maps, profiles take time to load. But you need to wait for them load completely before any change. Otherwise, some incorrect thing (for example some links will be disconnected) will happen and it takes you much time to investigate.

The way Boomi processes documents may be different from the programming languages you are using. So you have to change your mindset logically when working with Boomi.

Logging and debugging is a hard process when you execute processes on Atom. Hopefully, Boomi can visualize an execution just like the way it does when running on test mode.

Number of features (shapes) are limited, you need to use them flexibly to meet your needs. Otherwise, you need to write some source code with custom scripts.

Graphical ETL Interface that is simple

Large community and good resources

Integration with many platforms

The option for detailed logging on deployed processes would be a good additional feature.

More control over documents from a database

Delete multiple IDs from Salesforce at one time

Mapping: they have an auto mapping tool for 1 to 1 fields, but then also allows for very custom logic so that values can be passed in the most usable way.

Built-in integration to nearly every platform.

Total customization of processes.

It would be nice if it was easier to find what processes affect each other. In the folder structure, you have some of that ability, but because you can reuse the same logic across different processes it can be difficult to find the original source. Naming conventions are important.

The way they charge you per a connection is very useful as you can reuse connections more than once. The issue runs into limits, so before you start building, it is important to understand all the limits of all of your systems, and don't create a connection for each one or you are paying too much. This isn't something that was articulated well.

File profile

Interact with Groovy code

File treatments: It is quick to process them

Formatting dates

The ability to connect to any server, so that it is not necessary that the files reside locally

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.

If you have more complex integration requirements, you need to write lots of custom scripting in Javascript or Groovy. It takes some time for a software development team, for example, to become really productive in Dell Boomi environment since it requires a change in the mindset of a programmer.

Every connection type has a cost. When you run on a low budget, you need to think and have workarounds in your integration's architecture and design to overcome this.

Performance may be an issue with customs requirements in data processing. For example, if you have to process data in a sequential fashion, you will see a huge drop in performance since Boomi is optimized for parallel processing.

Boomi has a lot of built in connectors that make integrations faster and easier.

The tool is easy to use and has great visuals to help understand how a process works. There isn't a large learning curve.

Frequent updates to the platform.

New connectors are frequently added.

Great support documents and community.

Real-time integrations.

The dashboards are limited

Running Low latency improves performance but makes resolving issues very difficult

Unable to sign up for alerts for one process only. Alerts go out at an account level. If you want to get notifications for a process you need to build it into your application.

The folder structure of components can get messy if not well governed.

Easy to create duplicate components and not realizing that someone else in your company already created one.

Scripting could be improved. You don't know if you have errors in your code until you run the process.

Low Code, user-friendly UI

Various inbuilt connectors and features like Boomi suggests which makes development easier and faster

Readily available materials and fast response through Boomi communities and user guides with solutions to complex problems

For some transformation areas, we still have to use scripting, like for dynamically converting xml to csv or vice versa without defining a specific profile. These ideas are addressed in the communities.

Completely cloud based solution. No need to install any software or agent on local machine while integrating cloud systems. Although provides ability to integrate on premise solutions too by installing and local atom.

Best thing about Boomi is its relatively low learning curve. Its very easy to use for the developers.

Great tutorials and documentation available on their site.

Boomi supports a wide variety of systems and provides flexibilities to integrate home grown systems too.

Pricing is on a upper side comparing to other tools in market. However it does worth it in my opinion.

Although documentation is good but it lacks examples.

Cloud Integration

Atom and Molecule performance on both On-Premise and Cloud Deployments

Easy to Use Connectors and configure with out any difficulty

Wonderful support

NA

NA

NA

On-Premises Connectors (Disk/FTP/DB)

Cloud SaaS Connectors (Salesforce, Service Now)

Big Data Connectors

Cloud Storage Connectors (Azure, Amazon, GCP)

Nicer UI (more appearance - it's just my opinion))

Good Documentation on Developing Custom Connectors

Better Strategy in minimizing downtime while performing upgrades

After recently finishing my first small business focused Boomi integration here at SFCG, here are the top five things that are totally cool about the Boomi Atomsphere Platform:

Coding Not Required: This integration required sourcing data from one cloud app and writing to two different objects in another Oracle CX cloud app. This integration performs a web service call for the source data (QuickBooks Online) and then uses web services to write to two different entities (Oracles Sales Cloud – Accounts/Contacts) in another application. For more complex situations, Boomi does allow for coding using JavaScript or Groovy. However, no higher level coding was performed here. This process included 37 different steps.

Unique Data Processing: Boomi processes a single record at a time. This sounds similar to the way the current integration products work but it’s actually not quite the same. Most tools process a whole file (with multiple records) thru each step. Boomi’s methodology runs the record (or row of data), which is a basic unit of work, thru the process up and until you decide to combine it into a multi-record document. One reason a development engineer might find this interesting is that the developer designs a process to handle a single unit of work. Boomi handles the looping. Totally Cool!!!

Branching Processes: Branching allows you to start over with the source data to accomplish something else in your process. Only one source read is required to process a record thru multiple branches. Above we process all the source records into an Account entity, and then we start over with the original source data and process it into Contacts.

Storing Results for Error Handling: Result info easily captured. We can capture results and store them into a Dynamic Process Property.

And the TOP COOLNESS Reason. Every Integration methodology concept we configured into this integration helps builds a template for starting on the next. Some of the artifacts will even be re-usable.

Another cool feature is using the Email feature to email of process results is fairly simple and straightforward. I have written a blog article about this:

http://sfcg.com/four-steps-to-using-the-boomi-email-step-in-integrations/

The last cool feature I have actually written about is the Flow Control feature.

Boomi handles many integration tasks at a high level without the need for scripting pretty much at all. However, there comes a time when you just need to alter/manipulate/examine the document by groups, and most of the Step components generally cannot do that. However, you can use the Flow Control step.

The Flow Control Step is one component that is totally awesome. For example when using the process batch web-services in Oracle CX – Sales Cloud you can group the XML payloads in batches of 500. In your Boomi data Integrator process you can easily handle this issue with the Flow Control Step.

This step takes individual documents flowing into this step, and batches them in whatever is configured as a Batch parameter. It is typically followed by a combined step.

Sample Flow

Say Quickbooks as a source has 1800 records in their database. Through web-services we are provided with 1800 XML documents, one at a time. These documents flow thru the Flow Control Step, and only 500 (or less) at a time are processed. Then the next step combines the 500 that flowed into the step and creates a single document with combined information of the 500 records.

This would happen for document 501 thru 1000, and then 1001 thru 1500, and then 1501, thru 1800.

http://sfcg.com/boomi-integrations-the-coolest-feature-yet-the-flow-control-step/

The Data Process step has a cool feature for splitting records. However the XML piece has some reported issues. This is easily overcome with custom Groovy scripting.

Moving data between Salesforce and NetSuite. With the great and extensive open API that both of products offer, Boomi allows you to simply connect to the different endpoints, and drag-and-drop to create the workflow. In fact, when we first implemented Boomi, it was so easy to learn and adopt, that we took one of our accountants and turned them into our Boomi admin.

We also use it in on-boarding employees. When we first create an employee in our HRIS (syncHR), it automatically creates and syncs the user across to Concur, Workfront, Motivosity, etc.

We also use it to sync project data between Workfront and NetSuite. This allows us to have a simply but robust process in recognizing revenue related to projects and work being performed in Workfront.

Honestly, the user interface. It has a lot of room to improve to get aligned with our products it is working with. The design is intuitive, but somewhat clunky because of the interface. It seems to be about 10-years behind other products in this area. The UI is important, especially when you are trying to attract users that may not have a development background.