You are here:
Working with Implementations
An interface interrupts a process; the implementation includes the code that the application executes during that interruption.
You can build your own implementations and choose what data to incorporate to solve any problem. Implementations determine which data or metadata to use, how to use it, and the sequence in which to use it.
In implementations, an sObject can be an Opportunity item, Order item, or Quote item. The context header item is the Opportunity, Order, or Quote.
An implementation has four possible states:
-
Active: The active implementation is the implementation the interface calls.
-
Default: The default implementation is the implementation the interface calls when another implementation is not specified.
-
Both active and default: The implementation is the active implementation and the default implementation.
-
Neither active nor default: The implementation is neither the active implementation nor the default implementation.
Salesforce recommends that the default implementations provided in the managed package remain the defaults. When an implementation is marked as the default, but the name is not the same as the default implementation in the managed package, that default will not be executed. You cannot change a default implementation name.
An implementation can leverage third-party or legacy code. For example, you may have a legacy system that successfully implements a complex pricing structure. To use that process, you can call an interface implementation that links to and uses the existing process. You can also direct calls to any one of several different pricing systems, depending on the input. You can create a new implementation that combines customized code with calls to other products.
Before using external code, see the Salesforce document Apex Web Services and Callouts.
- Create a Customized Implementation
You can create an entirely new implementation or edit an existing implementation. In the following example, the ExtendedProductValidationImplementation implements the ProductValidationInterface. - Explore Implementations
The unmanaged package code provides sample starting points for custom business logic. - Managed and Unmanaged Apex Classes
You can edit code in an unmanaged Apex class, but you can't edit code in a managed Apex class. - Setting an Implementation
Your Vlocity package comes set with the default implementations. You can change an interface implementation setting to another provided implementation or to an implementation that you create. You only need to set the implementation once. - Adding a New Interface Implementation
After you have created a new implementation and associated Apex class, you can add that implementation to the appropriate interface.
