Clone and use the data processing engine definitions for Price Protection as-is, extend them to meet your business needs, or create definitions from scratch. To use a definition, you must activate it.
Clone Data Processing Engine Templates
Clone the Data Processing Engine templates readily available with Price Protection. When you clone a template, the cloned definition can be activated and used to detect product price changes. You can customize the cloned definition to add or edit the nodes, aggregation logic, and variables.
Create Custom Data Processing Engine Definitions
Create a Data Processing Engine definition from scratch if the predefined templates don’t meet your requirements. Ensure that the source objects used in the definition are available in the org and that you have Read and Create permissions for the objects.
If the data source objects used in the definition require access to Setup objects, ensure they’re enabled. For example, from Setup in Order Settings, enable Order if Order is a data source object.
For detailed instructions, see Create a Data Processing Engine Definition.
Activate a Data Processing Engine Definition
The admin can clone and customize any of the predefined Data Processing Engine templates that come with Price Protection, and activate the cloned definitions.
You can run an active definition with Flow Builder, or from within the Data Processing Engine builder. Based on how frequently the flow is scheduled, the associated data processing engine definitions are run. If you run a definition from within the builder, define input variables specific to that definition.
For detailed instructions, see Activate Your Data Processing Engine Definition.
Additional Learning Resources for Data Processing Engine
Learn more about how to best use Data Processing Engine.
| Resource | Description |
|---|---|
| Permissions to Work with Data Processing Engine | Information on permission sets and object access required for user profiles when you use DPE. |
| Run a Data Processing Engine Definition with Flows | Task-based topic on how you can run DPE definitions with Flow Builder. |
| Track Your Data Processing Engine Usage | Information on the type of data you can track with Data Pipelines. |
| Monitor Your Data Processing Engine Definition Runs | Topic explaining how to use Monitor Workflow Services to track the progress of your DPE runs. |
| Data Processing Engine Best Practices | Pointers on how to improve your experience working with DPE. |
| Data Processing Engine Limits | Considerations to keep in mind when you use DPE. |
| Troubleshoot Data Processing Engine Issues | Self-help for resolving errors in DPE. |
| Data Processing Engine Data Model | Architecture topic explaining object relationships in DPE. |
| Create definitions using Metadata API | A developer doc that explains how you can create a DPE definition by using APIs. |
| Run a Definition by Using a Custom Invocable Action | A developer doc that explains how you can run a DPE definition with an invocable action. |
| Know When a Definition Run is Complete by Using a Platform Event | A developer doc that explains how you can get notified when a DPE definition run is complete. |
- Data Processing Engine Template for Price Protection
Price Protection has a Data Processing Engine (DPE) that helps you transform data that’s available in your Salesforce org and writes back the transformation results as new or updated records. You can transform the data for standard and custom objects using Data Processing Engine definitions. After you set up a Data Processing Engine, you can use a flow to run it. Each run can be tracked using Monitor Workflow Services.