Run Prebuilt Data Processing Engine Definition for Collections Outbound Dialer
Clone, customize, and run the prebuilt Data Processing Engine definition, Filter
Collection Plans by Overdue Amount. After this definition is run successfully, use this definition
to create an actionable list of delinquent collections.
To open the prebuilt Data Processing Engine definition:
Customize Application permission
AND
Modify All Data
permission
AND
Collections and Recovery Admin permission set
To run the prebuilt Data Processing Engine definition:
Customize Application permission
AND
Modify All Data
permission
AND
Collections and Recovery Admin permission
set
AND
Data Pipelines Base User
By default, the prebuilt Data Processing Engine definition, Filter Collection Plans by Overdue
Amount, creates a dataset of collection plans and their corresponding accounts where the total
overdue amount is greater than 100. Customize this Data Processing Engine definition according
to your business requirements.
From Setup, in the Quick Find box, find, and select Data Processing
Engine.
Search for the prebuilt definition, Filter Collection Plans by Overdue Amount, and click
Save As.
Enter the name, API name, and save the changes.
Click the action menu of the cloned definition, and select
Activate.
Open the active definition, click Run Definition, and then click
Next.
Select one or more debug modes, and click Run Definition.
To monitor if the definition run succeeded or failed, go to Monitor Workflow Services, and
view the status.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
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.