Skip to main content

Anatomy of a Rule Execution Request

The steps below help to give a top-level understanding of how InRule is integrated with Salesforce. Please note these steps are a simplification that does not cover topics like caching, iterations, and multiple environments. It serves to show how the request moves through different Azure resources.

  1. The DecisionClient in Salesforce is called by a button or event. This generates a call to the Rule Execution App Service.
  2. The Rule Execution App Service makes a request to the Catalog Service, asking for a copy of the requested RuleApp.
  3. The Catalog Service Queries its SQL Server based database for a copy of the requested RuleApp.
  4. The SQL Server responds with the RuleApp.
  5. The catalog service responds to the Rule Execution App Service with the RuleApp.
  6. The RuleApp executes inside the Rule Execution App Service.
  7. Optionally, the RuleApp has an opportunity to query Salesforce for additional data needed to execute rules.
  8. The RuleApp completed execution
  9. The Rule Execution App Service relays the response to Salesforce, where the InRule for Salesforce App synchronizes changes