Customize Data Processing Engine Template Definitions
Customize an out-of-the-box Data Processing Engine (DPE) template definition to add
data sources or nodes, adjust transformation logic, or support business calculations not
included in the template.
Review the DPE template to understand how nodes are connected and referenced by downstream
nodes.
Cloning a template lets you safely modify logic in a new version without affecting the original.
Because cloning copies all nodes, you can use the template as a baseline to save time and
maintain consistency.
Keep these best practices in mind when modifying a template:
Make sure that you have the required setup, permissions, and object access for all
objects used in the definition. See Data Processing Engine Setup.
If you add new calculated outputs, make sure that the target fields exist and map them
correctly. For example, if a new forecast metric is required, create a custom field, then
add that field as a forecast measure in the forecast logic in the cloned definition.
From Setup, find and select Data Processing Engine.
Search and open the out-of-the-box template that you want to customize.
Templates are read-only. In the definition list, look for definitions marked as
templates.
Click Save As.
Provide a name and description for the new definition.
Verify the API name and process type and modify them if needed.
A company wants to see product
costs and profit margins in account forecasts. Standard templates focus on quantity and
revenue. To give demand planners visibility into margins:
Add custom measure fields to capture cost and margin.
Update the cloned definition to compute these values from data sources.
Write back results for forecasting and planning.
This customization helps planners make informed pricing and discounting decisions for
future periods.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.