Data Processing Engine Additional Information

Get to know additional deployment information for Data Processing Engine in Revenue Cloud.

Deployment Considerations 
  • Data Processing Engine objects have Draft and Active states.
  • The objects must be created in Draft state and activated later. The activation is done through API.
  • Configuration can’t be changed after an object is updated to Active state.
  • Set the state of the object to Inactive for any modifications, and then set the state to Active.

Other Information 

  • Data Processing Engine has dependencies on these components.

    • CRM Analytics or Data Cloud
    • Bulk API

  • You can deploy Data Processing Engine definitions from one organization to another. Both organizations must be on the same Salesforce release version.

Get Started with Revenue Management Developer Resources
Revenue Management Settings
Revenue Management Deployment
Deployment Workflows and Sequence
Deployment Considerations
Global Unique ID Setup
Managing Component States
Post-Deployment Steps
Deployment Scenarios
Object Deployment Reference
Metadata Deployment Reference
Additional Deployment Information
Product Catalog Management Additional Information
Salesforce Pricing Additional Information
Product Configurator Additional Information
Dynamic Revenue Orchestrator Additional Information
Usage Management Additional Information
Billing Additional Information
Business Rules Engine and Decision Tables Additional Information
Context Service Additional Information
Data Processing Engine Additional Information
Salesforce Contracts Additional Information
Product Catalog Management
Salesforce Pricing
Rate Management
Product Configurator
Transaction Management
Advanced Approvals
Dynamic Revenue Orchestrator
Usage Management
Billing
Revenue Management Associated Objects
Previous Versions