Five Fundamentals of Salesforce.com CRM Integration

Glenn Johnson,Toolbox.com

When integrating other systems with Salesforce.com CRM – and orchestrating affected business processes – you need to be able to work with Salesforce.com objects, metadata, bulk jobs, replication and lead conversion.


1. Objects. A business process integration solution like iBOLT allows you to perform all the required functions with objects. When working with Salesforce.com objects, you will want to be able to get the timestamp of any object, get the objects list, update the object structure and perhaps even merge objects. It is important to be able to dynamically get the objects list because of the ability of users and administrators to personalize the implementation.
2. Metadata. When working with Salesforce.com metadata, you will want to check the status of any metadata operation at any time. Obviously you will need basic CRUD operations (Create, Read, Update and Delete). And you will need to be able to retrieve and deploy metadata.
3. Bulk Jobs. Going beyond these basics, a sophisticated solution like iBOLT will give you the capability to orchestrate bulk jobs. These powerful batch operations are key to efficiency across multiple users. You will want to be able to check the status of bulk jobs, retrieve bulk job results and even abort bulk jobs.
4. Replication. Another key requirement for many organizations is the ability to selectively replicate their Salesforce.com data from the cloud to a secure enterprise storage server. With the iBOLT integration suite, you can replicate data locally from your salesforce.com implementation. You can replicate all data or simply last updates and last deletes as part of a particular iBOLT business process flow.
5. Lead Conversion. In Salesforce.com terminology, a lead is a potential customer that you do not yet want to add to your account list. Once a lead is ready to become an account the user can convert the lead which automatically creates an account (the organization or company record), a contact (the individual person record) and optionally as an opportunity (the specific potential deal being tracked).
Bringing IT All Together. With a business process integration solution like iBOLT, you can automate lead conversion in Salesforce.com. You may want to use iBOLT to check for the existence of similar accounts and contacts in your ERP system for example and apply business rules for validation, disambiguation and deduplication of data.
If your ERP system is JD Edwards, for example, then iBOLT can query F0101 and related tables for matching records. If you are running SAP, iBOLT can check things like ADCP and ADRP for address information. And for companies with multiple ERP implementations, it can even check both.
The five fundamental capabilities described here are the building blocks of business process orchestration between Salesforce.com and your ERP system. iBOLT makes it easy to design these business processes though a drag, drop and configure approach that lets you control the settings for these fundamentals rather than having to write cumbersome Java, C# or APEX code. For additional information, you can visit the iBOLT for Salesforce.com microsite and download the White Paper “Maximizing Benefits from Salesforce.com via Integration with On-Premise Applications.”