On June 20th, we had our Sugar Showcase webinar highlighting Magic Software's Integration Platform, which provides an enterprise-grade code-free, metadata-based approach to integration, letting IT and business users easily automate and streamline business processes between different applications and databases without programming or complex middleware. Magic Software's integration platform makes it easy to integrate Sugar with any ERP, email, social media, and other business apps.
Thank you to everyone who participated in this webinar. Below is the video recording, slide deck, and Q&A.
If you have questions about wMaps or would like an individual demo, feel free to contact us.
We do not currently have a pre-built connector for Sage X3. However, we've done a number of different integrations with Sage. If we haven't done one in the America's team, chances are somebody worldwide has done it. As web services, we leverage our web services connector for that. We do have the ability to create custom connectors. So, if there's something out there that somebody wants a custom connector for, we can do that. Over time, our development team is coming up with new connectors with every version.
It depends on how elaborate the business process is, and on how many data points we’re sinking. And the whole point of implementing a tool to us is that it's a lot simpler than doing a traditional point-to-point integration. Regardless of how complex or simple, it would be a lot easier than just writing it in code. Some of the more complex ones are the ones that have a little bit more complex logic, so if someone is simply creating sales orders, or passing, the typical ones that we see with, for instance, SugarCRM and ERP.
Typically, you're going to have opportunities to sales orders, products, items and products matching up, and then accounts and contacts, and leads will often become accounts. Those are relatively the most common, and the simplest if there's no validation. The ones that get a little bit more elaborate are different types of eCommerce applications where, before you create a sales order, you have to do some validations against. Sometimes, there are promotions at the time of the week and you have to calculate the day and something of the sort. Those can be a little bit more work, but none of these are difficult or challenging, and I want to emphasize, this is nothing we haven't done before. Not just for America's team, but for worldwide. There's no business process out there that is so elaborate, we've never seen it before.
We work with both of those. We're as secure as whatever networks we're working with are behind. We can work with encryption, we can work with IS and SSL. At the very top level, when we connect to an application, we usually need a log in that has permissions to do the bare minimum of whatever we need to do. So, if that means, if we're reading from the database, we just need to read the database, if we're reading and writing, we need a user that reads and writes.
We can also act as a second layer of security for your team, so, theoretically, the demonstration I just did, anybody who can log into EVS, and create a new customer, is going to create a new customer in your Sugar environment. However, we can act as a second level of security where we can get to all the data points using schema discovery, so, we can do a lookup against that individual’s login, and before we do that sync, we can do a query to see if that person has permissions or has the right role to do that, and if not, we can stop the sync, and send it to an email to someone saying: "so and so is trying to do something they're not supposed to do."
The answer is yes to all of those. We're not just a two-way integration sync. We've integrated CRM's like Sugar with ERP's, but also implemented an eCommerce application to pass data, to create orders in Sugar, and then we pass those to ERP's, we've simultaneously implemented PLM applications to ERP's to manage the items, and even Human Resources applications to create and manage employees as well. Through our flows, we can do multiple different directions, and we can do batch or real-time updates, depending on the business process required.
We can get ahold of all or none of the data. When we do our data syncs, we can pass whichever data you wish over to the CRM, so I think that's more of a question directed at who would ever be implementing the Sugar CRM, but, hypothetically speaking, let's say we were doing an integration between a SAP and a CRM environment. The salesman may very well need to see the account information, some of the customer contact data, but the salesman may not necessarily need to see all the order history, or all the credit terms, and all that elaborate stuff that you have, that accounting data that you have in the ERP, or the SAP environment, so through our mappings, we can pass as much or as little information as you want.
And that's why we build our solutions per our customers’ needs. When I opened those mappings, as you can see on both sides of those mappings, there were lots of index fields. You may not want all of them, you may just want a few of them. So, that's a case-by-case basis.