Loading
Salesforce now sends email only from verified domains. Read More
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Configure Apex Hooks in a Product Discovery Procedure Plan

          Configure Apex Hooks in a Product Discovery Procedure Plan

          Use Apex sections in a Product Discovery procedure plan to run custom pricing logic, such as fetching prices from an external system. The order of Apex and Pricing sections determines how prices are applied. You can include multiple Pricing and Apex sections, but only one Qualification section.

          Required Editions

          View supported products and editions.
          User Permissions Needed
          To create, update, and delete pricing procedures: Salesforce Pricing Design Time User or Procedure Plan Access
          To use pricing procedures: Salesforce Pricing Run Time User
          To define, edit, delete, set security, and set version settings for Apex classes: Author Apex
          • Make sure the Apex class implements RevSignaling.SignalingApexProcessor.
          • Confirm that the class is packaged and available in your org namespace.
          • Make sure the External ID field is populated for your Product2 records if used in pricing.
          • Only one Qualification section is supported. You can include multiple Pricing and Apex sections.
          • To create a procedure plan and add base sections, see Creating Procedure Plan Definitions Using Templates.
          1. From Setup, in the Quick Find box, enter Apex, then select Apex Classes.
          2. Select New to create a new Apex class.
          3. In the class editor, enter the class definition and save the definition. When you activate a procedure plan, Salesforce checks the order of Qualification, Pricing, and Apex sections. Activation fails if the order doesn’t follow the supported sequence.
          Example
          Example

          Examples of supported and unsupported section orders:

          • Supported: Apex , Pricing , Apex
          • Supported: Apex , Apex , Pricing
          • Supported: Apex , Apex , Pricing , Apex , Apex
          • Supported: Apex , Apex , Pricing , Pricing , Apex , Apex
          • Unsupported: Apex , Pricing , Apex , Pricing , Apex
          • Unsupported: Apex , Pricing , Apex , Apex , Pricing , Apex
           
          Loading
          Salesforce Help | Article