Skip to main content

Salesforce Integration Architecture

This section discusses the steps needed to integrate InRule with Salesforce. Using this scenario InRule components are hosted on Microsoft Azure.

This guide will provide the instructions for setting up all the components below:

InRule for Salesforce solution architecture diagram showing Salesforce components (Lightning Page, Event Triggers, Salesforce Flow, Apex, Classic Button), InRule for Salesforce components (Lightning Component, Decision Client, Configuration), and the InRule Decision Platform (irServer Rule Execution Service for Salesforce, irCatalog Catalog Service, InRule Metrics) hosted self-hosted in Azure or InRule SaaS, with data flowing to Application Insights

Catalog App Service and Azure SQL Database​

A Catalog service will be used to store Rule Apps that will be consumed by the Rule Execution App Service. This Catalog Service will be hosted as an Azure App Service. The back end of the Catalog Service utilizes an Azure SQL Database for retrieval and persistence of Rule Applications.

Rule Execution App Service for Salesforce​

The Rule Execution App Service is responsible for loading Salesforce entity data, executing rules against loaded data, and responding to Salesforce with rule execution results.

InRule for Salesforce App​

The InRule for Salesforce App contains Apex classes, as well as custom settings and objects. It is configured to communicate with the execution service over REST.