Salesforce developers overview - InCountry

Salesforce developer overview

InCountry’s 2GP Managed Package for Salesforce makes it possible to use Salesforce or Hyperforce instances from multiple regulated locations. Multinational companies can continue to run a single global Salesforce org or a few regional orgs. The package handles data residency requirements for each configured country. 

InCountry Managed Package for Salesforce

InCountry’s 2GP Managed Package for Salesforce makes it possible to use Salesforce or Hyperforce instances from multiple regulated locations. Multinational companies can continue to run a single global Salesforce org or a few regional orgs. The package handles data residency requirements for each configured country.

InCountry Salesforce Managed Package

InCountry offers the following components for Salesforce

Web Services

Data Residency Application for Sales, Service and Experience Clouds

The application provides Sales, Service and Experience Cloud Lightning Web Components that look & feel as the core Salesforce components. For example, for Sales Cloud Customers can use Detail View, Highlights Panel, Related Lists, List Views, Reports and other components. Every component intercepts User’s request, verifies their permission and splits the data flow: non-regulated data and metadata are transmitted from Salesforce Backend, regulated data is transmitted from InCountry PoP via a browser request (Javascript Fetch API). The client-side mutual TLS is established using JWT that are generated for every action on a page. Our Product team ensures that all custom LWCs are updated regularly and the connection between LWC and InCountry PoP (point of presence) is secured.

JavaScript SDK

Many Salesforce Customers have their own custom LWCs or Aura components. InCountry’s JavaScript SDKs works with both frameworks, and it helps to satisfy Data Residency requirements without implementing custom integration with InCountry PoP. Customers can just import InCountry ES modules into their code and start  performing operations with the Point of Presence: CRUD, Search, Serverless, etc. The SDK handles access control checks, JWT authorisation and authentication and client-side connection to InCountry PoP behind the scenes. It is especially useful for customers who a running Redacted model, where regulated data cannot be transferred to Salesforce server.

Apex SDK

It provides an Apex interface to InCountry Point of Presence operations, such as CRUD, Search, Add Attachment, Hash, etc. The SDK is synchronous, so any Customer who is running their own custom Apex, can call Apex SDK actions from Triggers, Batch Jobs, Queueable Jobs, Future Jobs, Anonymous Apex, Controllers, Invocable Actions and any other Apex code. Unlike JavaScript SDK, Apex SDK establishes a server-side connection from Salesforce Backend to InCountry Point of Presence. The connection is secured by the OAuth2 flow.

Salesforce Cross Border

This solution can help customers who are running several Salesforce or Hyperforce instances to replicate and anonymize regulated data in near-real time. Let’s say, a customer has a local Hyperforce instance in China and a global Salesforce org in US, and they want to replicate some portion of Chinese records from China to US for global reporting. The data must be anonymized due to regulation restrictions, and the connection must be secure. Salesforce Cross Border application uses InCountry Proxy to perform near-real-time migration. It supports retries, guaranteed order of events, logging and monitoring.

InCountry UI API

This API works similarly to Salesforce UI API, and it provides high-level access to InCountry CRUD operations. Customers, who a running their own Lightning Web Components, can use the API without worrying about non-regulated and regulated records. The API automatically splits data flow based on the package configuration. All regulated records and fields are stored to the InCountry PoP, all non-regulated records and fields are stored to the Salesforce database.