Valence is a tool designed to make your life easier. We’re happy to get you started with it.
The first thing you should understand is that Valence installs into a single Salesforce org and does all of its magic from inside that org. There is no external middleware server involved, which means data moves directly between your Salesforce instance and whatever system you want to exchange information with.
We’ve designed Valence to be intuitive for admins to use, and easy to extend when custom code is needed.
Start here to develop a basic understanding of the component parts of the Valence engine.
- Overview — Valence is a middleware engine that lives inside your Salesforce org. Data movement is handled with direct connections between Salesforce and external systems. There are several building block concepts that are important to understand in order to configure Valence.
- Configuration Files — Valence configurations are stored as Custom Metadata Type records, and can easily be moved between Salesforce environments.
- External Systems — Valence reaches out using HTTP to exchange data with external systems. External systems can also call into Valence using the Apex REST API.
- Custom Extensions — Valence is designed to be extensible, and provide places for custom code and logic to be added. These extensions are gracefully integrated into the UI and behavior of Valence so that users can configure and work with them as easily as they work with standard Valence features.
We have guides to help you understand certain topics in more detail:
- Sending Realtime Records To Salesforce
- Using Dynamic Configurations in your Extension
- How to Design a Complementary Valence API
- Building a Configurable Filter that Ignores Records Based on User-selected Cutoff Date
- Using Valence Between Two Salesforce Orgs (aka Salesforce to Salesforce)