Integration Builder - An Overview
  • 20 Jul 2021
  • 3 Minutes to read
  • Contributors
  • Dark

Integration Builder - An Overview

  • Dark

Integration Builder - An Overview

IB is a service that can be used to write business logic by connecting it to the backend system and to read the business data as a rules engine. The rules engine is nothing but a series of business rules that are applied for a particular function within the business process. 

To sum it up, in the EdgeReady Cloud, the Integration Builder is primarily used to build the rules engine. The logic built in the Integration Builder can accept various types of data as input and process to generate the expected output, which can be shared with the other components of the EdgeReady Cloud. 

Why do we need an Integration Builder?


For an App, the integration builder is used to fetch the data from the backend system and helps to determine what service can be applied to the particular data. 

With respect to fetching data from the system, the IB:

1. To build and execute business and integration logic for the App

2. To integrate the apps with various types of "on-site" systems

3. To encapsulate one or multiple functionalities

4. To accept various types of data as input and process to generate expected output, which can be shared with other components of the EdgeReady Cloud. 

The 3rd party servers such as SAP, Salesforce, and other External Databases can be integrated within the EdgeReady Cloud platform.

How to access the Integration Builder? 


The integration builder can be accessed by double-clicking the BOS component of the App Process Modeler. It can either be opened in the same tab or in a new tab

Once dragged and dropped, it is given an appropriate name. 


The Integration Builder Canvas

The Integration Builder in the EdgeReady cloud platform appears as:



  1. The code blocks on the left are services that can be used within the device for fetching data. They can be dragged and dropped in the canvas area. 
  2. There is a search bar at the bottom of the blocks where a user can search for an appropriate block for quick access. 
  3. The BOS, on the other hand, has input, output for each service block. New input and outputs can be created in the IB; Additionally, existing variables can be fetched from the App Process Modeler or the App Designer
  4. For each service, the Local Variables and Session Variables can be selected appropriately. 
  5. These services play a predominant role in the application functionality both in the offline and online mode.
  6. The canvas area on the center is where the rules engine is built for different run-time lanes

Similar to the App Behavior section, the code blocks in the integration builder are also based on the concepts of Scratch Programming. 

Refer to the Understanding Scratch Programming section for more information on Scratch concepts. 

The EdgeReady Cloud consists of 3 layers -

The ERC layers:

  1. FrontEnd Layer: UI/UX for different users.
  2. Cloud Layer: It is the core of the platform that is accessed during runtime.
  3. On-Plugin Layer: Also known as the EdgeReady Plugin that is installed on the client system. 

The EdgeReady Runtime (Lanes):

  1. These lanes decide where all details and logic are executed. 
  2. Whether the business rules are executed on-device, on-plugin, or on-cloud are decided by the EdgeReady Runtime. 
  3. No Block can function without defining a particular lane from the EdgeReady runtime in which it functions. 
Purpose and DescriptionCode Block
  • On-Device: They are used exclusively for Offline Apps. Data is retrieved from local DB. (EdgeReady DB)
  • On-Plugin: Data is fetched from the backend server. (Eg: SAP)
  • On-Cloud: Data is fetched from the Cloud. (Eg: Salesforce)

Plugin Lane

  1. In some cases, like SAP, the BOS is run on-premise within the cloud lane.
  2. In order to access data from the plugin lane, it requires an additional Plugin. 
  3. This plugin primarily helps to access data that are behind the 3rd party‚Äôs firewall. 
How to access the PluginPlugin on Canvas
  • The spaces are provided to enter the credentials (Username & Password) to access the respective plugin. 
  • There is also a Select option for selecting the appropriate adapter for the plugin. 
  • For direct cloud access, the data can be accessed using a URL to a 3rd party server and no Plugin is required. 
The Plugin lane cannot independently exist without an On-Cloud lane. 


Was this article helpful?