Integrating Salesforce with InforLN using Azure Integration Services - CloudFronts

Integrating Salesforce with InforLN using Azure Integration Services

Introduction

Integrating Salesforce with InforLN is a critical task for organizations looking to streamline their sales and billing processes. With the AIS Interface, businesses can efficiently manage data flow between these two platforms, reducing manual effort, enhancing visibility, and improving overall organizational performance. In this Blog, it shows the detailed information for integration between Salesforce to InforLN. The AIS Interface is intended to Extract, Transform and Route the data from Salesforce to InforLN. The steps for integration would be same for different entities.

Many organizations need Salesforce to InforLN integration because of the below reasons:

  1. Connecting their Sales and Billing process because Sales process is handled by Salesforce and billing process is handled by InforLN.
  2. Visibility of the organization performance is present in the single system.
  3. Remove the double work that Accounts Team and Sales Team needs to complete the sales to billing process as Integration can handle the overall organization business process.

Event Scenario

Pre-Requisites:

  1. Create API management and create APIs for specific entities.
  2. Create Service Bus and Subscriptions inside Service Bus.
  3. Create Function App and Service Bus topic triggered function app.
  4. Create App Configuration.
  5. Create Application insight for monitoring the logs.
  6. Create Storage Account.

Process Steps:

  1. Salesforce authenticates with AIS using Bearer Token and sends a HTTP request for Customer entity data using PUT method to AIS endpoint.
  2. Based on Policies configured in AIS the message (along with Method, Entity and Payload) is routed to specific subscription of a service bus topic.
  3. A Service Bus Topic Triggered Azure Function listens to the Topic Subscription on active messages being present in it.
  4. This Azure Function converts it into a specific format and sends it to Consumer i.e. Infor Ln endpoint.
  5. Consumer in turn returns the status code back to Azure Function.

On Demand Load Scenario

Pre-Requisites:

  1. Create Logic App.
  2. Create API management and create APIs for specific entities.
  3. Create Service Bus and Subscriptions inside Service Bus.
  4. Create Function App and Service Bus topic triggered function app.
  5. Create App Configuration.
  6. Create Application insight for monitoring the logs.
  7. Create Storage Account.

Process Steps:

  1. Based on an on-demand triggered Logic App a HTTP request is sent to Salesforce API using salesforce connector available in logic app in order to get contacts data at a time.
  2. Salesforce returns the contacts entity data.
  3. Based on Policies configured in AIS the message (along with Method, Entity and Payload) is routed to specific subscription of the service bus topic.
  4. The Service Bus Topic Triggered Azure Function listens to the Topic Subscription on active messages being present in it.
  5. This Azure Function converts it into a specific format and sends it to Consumer i.e. Infor LN endpoint.
  6. Consumer in turn returns the status code back to Azure Function.

Conclusion

Based on the above Integration scenarios Azure Developer can easily navigate for the integration implementation and they can choose between Event Driven or On-Demand based on the business requirement. This integration not only simplifies complex processes but also eliminates redundant tasks, allowing teams to focus on more strategic initiatives. Whether your organization requires event-driven or on-demand integration, this guide equips you with the knowledge to implement a solution that enhances efficiency and supports your business goals.

We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at [email protected]


Share Story :

SEARCH BLOGS :

FOLLOW CLOUDFRONTS BLOG :


Secured By miniOrange