How Apex hooks work

Apex hooks are included at multiple points in the Deal Manager process flow. These hooks enable you to use an Apex class to customize the data returned by a specific point in the process. For each Apex hook, use of a custom Apex class at that point is optional.

Each Apex hook has a specific interface or interfaces that you must use to create the Apex class that is called for the hook.

Each Apex hook has a corresponding field on the Product Selector Configuration or other related object. This field indicates which Apex class should be called for an Apex hook, for any Add Lines or Line List component mapped to the Product Selector Configuration.

Multiple interface versions

New inputs or outputs may be required for a given hook. However, to maintain backwards compatibility, we cannot change the signature of an existing interface. Instead, we create a copy of the interface, rename the copy, and then add the new inputs or outputs to that copy.

When this occurs:

• The original and copied services are included in the package.
• Implementations that use the copied version of the interface will continue to work.
• Future implementations will use the newest version.

Apex hooks summary

The following table lists Apex hooks, their associated component or modal, and corresponding Product Selector Configuration field or a field on another mapped SObject.