Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More
Table of Contents
Filter by (0)Add
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
            Search all of Salesforce Help
            Understand the Order of Execution for Place Sales Transaction

            You are here:

            1. Salesforce Help
            2. Docs
            3. Agentforce Revenue Management

            Understand the Order of Execution for Place Sales Transaction

            When you create or update a quote or order using the Place Sales Transaction API, Revenue Management (formerly Revenue Cloud)processes the request through a defined order of execution. This order describes how configuration, pricing, Apex hooks, and automation run during transaction processing. Understanding this order helps you determine where pricing logic runs and how context data is processed when using Place Sales Transaction.

            Required Editions

            Available in: Lightning Experience
            Available in: Enterprise, Unlimited, and Developer Editions of Revenue Management (formerly Revenue Cloud) with the Revenue Cloud Advanced license.

            When Place Sales Transaction processes a request, Revenue Management performs these steps in sequence.

            1. Saves the sales transaction header.
              1. Executes triggers associated with the transaction header.
              2. Synchronizes supported context data back into the transaction context when context data is included in the request payload.
            2. Hydrates the transaction with data required for configuration and pricing.
            3. Applies applicable configuration logic to the transaction.
            4. Resolves Amend, Renew, and Cancel (ARC) data required for the transaction.
            5. Validates the transaction using ARC validation rules.
              Important
              Important ARC validation runs before the pre-pricing Apex hook. If you use Apex hooks to modify fields such as Start Date or Quantity, those changes bypass ARC validation and can produce unexpected results. To ensure proper validation, update fields like Date and Quantity in the request payload before calling Place Sales Transaction.
            6. Performs pricing.
              1. Runs the pre-pricing Apex hook, if defined.
              2. Runs pricing logic.
              3. Runs the post-pricing Apex hook, if defined.
            7. Persists data from the transaction context.
              1. Executes triggers for affected records.
              2. Synchronizes supported context data back into the response when context data is included in the request payload.
            8. Executes record-triggered flows and other custom logic based on the persisted data.
             
            Loading
            Salesforce Help | Article