--- schema_version: "1" id: 6538894a0f3201168116d22654ddd9b73d1d2c312657a9fbe1ca86101157d873 title: Data Processing Engine Workflow collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dpe_workflow.md canonical_url: https://help.salesforce.com/s/articleView?id=ind.dpe_workflow.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 643975fcb4191061c47467dbdae961875a5a8f61e58e5d6c8d342cc244947908 description: Build Data Processing Engine definitions in CRM Analytics and Data 360 runtimes. Use nodes to select data sources, add the data transformation logic, and configure target writeback destinations for the transformation results. Run and monitor Data Processing Engine definitions. products: - Cross Cloud release: "264" --- # Data Processing Engine Workflow Build Data Processing Engine definitions in CRM Analytics and Data 360 runtimes. Use nodes to select data sources, add the data transformation logic, and configure target writeback destinations for the transformation results. Run and monitor Data Processing Engine definitions. ### Required Editions
View supported editions.
## Define Your Business Requirements Plan your Data Processing Engine definition based on the business problem or process that you want to configure the definition for. - Define the business requirement such as reporting, analytics, data integration, and real-time insights. Determine the volume of data that you want to process and the frequency of updates, so you can decide the runtime where you can run your Data Processing Engine definitions. - Make a list of the data sources needed for your data processing such as Salesforce data, external databases, custom objects, and CSV files. - Determine the types of data transformations such as aggregations, joins, filters, and calculations. - Decide the destination where you want to write back the transformed data, such as objects, datasets, or Data 360 objects. ## Design Your Definition [Create your Data Processing Engine definition](https://help.salesforce.com/s/articleView?id=ind.dpe_create.htm&release=264.0.0&type=5 "Manage complex data transformations and integrations in your org by using Data Processing Engine definitions.") and configure nodes to select data sources, transform data, and write back the transformed results. - Add data source nodes for each of the definition's data sources. See [Add Data Sources to Your Definition](https://help.salesforce.com/s/articleView?id=ind.dpe_create_a_node.htm&language=en_US). - Use nodes such as append, filter, formula, and join to transform the selected data. See [Add Transformation Nodes to Your Definition](https://help.salesforce.com/s/articleView?id=ind.dpe_create_transformation_nodes.htm&language=en_US). - Use input variables to define default values, filter records and create formulas. See [Use Input Variables to Define Dynamic Processing Rules](https://help.salesforce.com/s/articleView?id=ind.dpe_define_input_variables.htm&language=en_US). - Add writeback object nodes to define where the transformed data is written back. See [Add Writeback Object Nodes to Your Definition](https://help.salesforce.com/s/articleView?id=ind.dpe_configure_writeback_object_node.htm&language=en_US). After you’ve designed your definition, activate it. You can [preview the definition](https://help.salesforce.com/s/articleView?id=ind.dpe_data_preview.htm&language=en_US) and [run it from the builder with debug modes](https://help.salesforce.com/s/articleView?id=ind.dpe_run_builder.htm&language=en_US) to validate whether the definition transforms data as per the business requirements. ## Schedule Definition Runs Run the definition as part of the business process that it transforms and writes back data for. Run the definition based on a schedule or based on triggers by using Salesforce Flow. Or, trigger runs from external systems - [Use the Action element in a flow](https://help.salesforce.com/s/articleView?id=ind.dpe_run.htm&release=264.0.0&type=5 "After you activate a Data Processing Engine definition, run it as part of a business flow or create a flow to run only a definition. You can also run a definition in a scheduled flow."). If an integration requires to run the definition, use the [custom invocable action](https://developer.salesforce.com/docs/atlas.en-us.industries_reference.meta/industries_reference/dpe_actions_run_data_processing_engine.htm). - [Use Monitor Workflow Services to track the status of definition runs](https://help.salesforce.com/s/articleView?id=ind.dpe_monitor.htm&release=264.0.0&type=5 "Monitor definition runs to review the status of your definition runs. On Monitor Workflow Services, you can analyze key details of definition runs such as count of records processed and written back, analysis of latest and previous runs, and reasons for the failure of the latest runs."). To track the overall status of runs and their tasks, use the Batch Job record that's created for the run. The name of the Batch Job record is the same as the definition. #### See Also - [Create a Data Processing Engine Definition](https://help.salesforce.com/s/articleView?id=ind.dpe_create.htm&release=264.0.0&type=5 "Manage complex data transformations and integrations in your org by using Data Processing Engine definitions.") - [Data Processing Engine Nodes](https://help.salesforce.com/s/articleView?id=ind.dpe_nodes.htm&release=264.0.0&type=5 "In Data Processing Engine, nodes are the basic building blocks that let you construct complex data processing flows. Nodes represent specific operations or transformations that can be performed on data. Each type of node lets you transform your data in a different way.") - [Use Input Variables to Define Dynamic Processing Rules](https://help.salesforce.com/s/articleView?id=ind.dpe_define_input_variables.htm&release=264.0.0&type=5 "Define flexible data processing rules by using input variables to define default values, filter records, and create formulas. To dynamically control the data filters and formulas at run time, create variables without values and use them to configure Filter and Formula nodes. During a definition run, specify variable values based on your specific requirements. For example, to filter opportunities above a certain value for different fiscal years, set a default value for the input variable and then update it when you run the definition.") - [Run a Data Processing Engine Definition in Flows](https://help.salesforce.com/s/articleView?id=ind.dpe_run.htm&release=264.0.0&type=5 "After you activate a Data Processing Engine definition, run it as part of a business flow or create a flow to run only a definition. You can also run a definition in a scheduled flow.") - [Monitor Data Processing Engine Definition Runs](https://help.salesforce.com/s/articleView?id=ind.dpe_monitor.htm&release=264.0.0&type=5 "Monitor definition runs to review the status of your definition runs. On Monitor Workflow Services, you can analyze key details of definition runs such as count of records processed and written back, analysis of latest and previous runs, and reasons for the failure of the latest runs.")