Portfolio

Sage 200 Boomi integration

Our Boomi integration developer team designed a custom API to achieve the first ever Sage 200 Boomi integration with Salesforce and Advanced Cloud School.

Sage 200 Boomi integration in education represented by digital connections

Technical brief

Building the first Sage 200 Boomi integration

Our client’s goal was to connect Sage 200, Salesforce, and Advanced Cloud School using Dell Boomi integration platform. We achieved this by creating a brand new Sage 200 Boomi connector, as well as using the Boomi Salesforce connector and the Cloud School API.

Dell Boomi integration logo
Salesforce CRM software logo
Sage finance software logo
Advanced Cloud School logo

As a result, the client has automated data sync to reduce the workload of its sales, finance, and administrative teams.

Curious how we performed this Sage 200 Boomi integration project? See the full story below.

The full story

The context

No more manual data entry

The client, a group of UK independent schools, had the goal of eliminating manual data entry in its sales, finance, and administrative teams. It was clear to the client’s technical team that a data integration solution was needed for three systems: Salesforce, Sage 200, and Advanced Cloud School.

 

Rather than a constant flow of data between the three applications, the client wanted each system to send data based on certain conditions.

 

First the sales team would enter a potential student’s data into Salesforce. When a particular set of student data was complete, only then would Boomi sync that data with Cloud School and Sage. This would create or update the student information in Cloud School and raise a purchase order in Sage.

 

At this stage the finance team would collect the payment and add that data to Sage, and the administrative team would input details such as the name of each student’s tutor into Cloud School. Once the data was complete, Boomi would push that information back into Salesforce. Thus Boomi would digitise and automate all the manual data entry that these three systems had required.

 

Convinced that Boomi was the most appropriate platform, the school looked for assistance from a Boomi Partner.

The plan

Digitise and automate with Boomi

Based on our extensive record of API integration services, the client opted to work with our Boomi integration developer team.

 

Our proposal was to create five sets of data transfer, as follows:

 

  1. Salesforce to Sage 200
  2. Sage 200 to Salesforce
  3. Salesforce to Cloud School
  4. Cloud School to Salesforce
  5. Cloud School to Sage 200

 

For greater speed, we planned to achieve this with Boomi low-code integration tools and custom Java code where necessary. The Salesforce integration would be relatively straightforward, as we could use the pre-made Boomi Salesforce connector. For the Cloud School integration we would have to use the Boomi HTTP Connector and a RESTful API.

 

However, the real test of our skills came from the Sage 200 Boomi integration. There was no pre-existing Sage 200 Boomi connector and no Boomi documentation, which meant we had to effectively create a Dell Boomi custom connector from scratch.

The execution

Custom Sage 200 Boomi integration

For the sake of efficiency we broke the project into two integrations: Salesforce with Cloud School and Salesforce with Sage 200. This enabled two members of our Boomi integration developer team to save time by working on the integrations simultaneously. For development and testing, we performed the Salesforce, Cloud School, and Sage 200 Boomi integration on our own cloud Boomi instance. Our developers worked in agile sprints throughout the project, keeping the client informed via regular show-and-tell sessions.

 

On the Cloud School side, we used Boomi to generate the access tokens that Cloud School requires as a security feature. This enabled us to take data from Salesforce and transform it into the right format before pushing it into Cloud School. Then we were able to achieve the connection from Cloud School back through Boomi to Salesforce, using the Boomi Salesforce connector.

 

At the same time our second Boomi integration developer was designing the Sage 200 Boomi integration. This required building an entirely custom RESTful API with the OAuth2 authorisation framework.

 

With all integrations completed, our developers carried out testing and then implemented the solution on the client’s on-premise Boomi instance.

The result

New Sage 200 Boomi connector

As planned, the client received a fully automated data flow between their sales, finance, and administrative teams. Our decades of integration experience allowed us to overcome the technical challenges en route and provide the first Sage 200 Boomi connector.

 

Post-implementation, we gave the client a hand-over session with full details of the data flow. This enabled the client’s technical staff to add additional integration steps via the low-code Boomi platform if needed. This future-proof and scalable platform was exactly what the business needed to drive its digital transformation further.

Overcome any integration challenge

This Sage 200 Boomi integration project is just one of the many innovative solutions we can deliver. If you’re in need of custom API integration services, get in touch — we’re always up to the challenge.

Info

17th August 2020
Integration, Dell Boomi, Salesforce, Sage, Cloud School

Privacy Preference Center

Necessary

Advertising

Analytics

Analytics cookies collect information that is used either in aggregate form to help us understand how our Websites are being used or how effective our marketing campaigns are, or to help us customise our Websites for you.

Google Analytics
The cookie _gcl_au is used by Google Analytics to understand user interaction with the website.

For example, in order for Google Analytics to determine that two distinct hits belong to the same user, a unique identifier, associated with that particular user, must be sent with each hit.

The analytics.js library accomplishes this via the Client ID field, a unique, randomly generated string that gets stored in the browsers cookies, so subsequent visits to the same site can be associated with the same user.

By default, analytics.js uses a single, first-party cookie named _ga to store the Client ID, but the cookie's name, domain, and expiration time can all be customized. Other cookies created by analytics.js include _gid, AMP_TOKEN and _gac_. These cookies store other randomly generated ids and campaign information about the user.

Google Analytics
_gcl_au, _gid, _ga, gtm_preview

Other

WordPress uses cookies for authentication. That means that in order to log in to our WordPress site, you must have cookies enabled in your browser.

There are two types of cookies set by WordPress.
1 — Session cookies — These are ‘strictly necessary’ cookies as WordPress will not be able to function without it.
2 — Comment cookies — These are not ‘strictly necessary’ cookies and are set when users leave a comment on a post.

Wordpress Session cookies:
Users are those people who have registered an account with the WordPress site.
wordpress_[hash]
wordpress_logged_in_[hash]
wordpress_test_cookie
wp-settings-{time}-[UID]

Wordpress comments:
Comments are usually turned off by default.
If by chance they are still active on a post, asides being turned off when spotted, data from these are not saved by Influential.
- When visitors comment on a post, they too get cookies stored on their computer. This is purely a convenience so that the visitor won’t need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:
comment_author_{HASH}
comment_author_email_{HASH}
comment_author_url_{HASH}

Wordpress, Intercom
comment_author_{HASH} comment_author_email_{HASH} comment_author_url_{HASH} wordpress_[hash] wordpress_logged_in_[hash] wordpress_test_cookie wp-settings-{time}-[UID]
intercom-id-[app_id],intercom-session-[add-id]