Running the PDO flow
Triggering the PDO flow
Once you activated the Direct Action as explained in Configure your Org and apps for using the PDO flow, the flow will be triggered automatically each time a Lead is created via the ways specified in the Direct Action trigger (e.g. User Insert).
If you set up a Macro for the flow, you can use it in a single or scheduled DAP Job, trigger it in a list view's Action Launcher, etc.
Sending notifications
If you set up emails or notifications to be sent, by default these are sent as follows, unless you changed the Send Notification flow actions in this regard:
| Email name | Sent when | Recipient |
| PDO Convert into Account | Converting the Lead as new Contact to an Account | Account Owner |
| PDO Convert into Contact | Converting the Lead into an existing Contact | Contact's Account Owner |
| PDO Convert into Person Account | Converting the Lead into a Person Account | Person Account Owner |
| PDO Linked to ABM Account | Linking the Lead to an ABM Account | ABM Account Owner |
| PDO Merge Duplicate Leads | Merging the Lead into an existing Lead | Owner of the master Lead |
| If a Lead was not merged, converted or linked to an Account, but instead routed with SRR, mails and notifications will be sent according to the SRR Assignee settings. | ||
Checking the results
After the flow has finished, you can view the results in the PDM Flow Log. Users with the “Plauti Data Orchestration” Permission set have access to the log. The log states the route the Lead followed in the Status column, e.g. “New Lead converted as new Contact”.
Phone validation requires Country
Note that for RV phone validation to work, records must have a country filled in.
Set Use Round Robin to FALSE
Make sure the default field value for the Use Round Robin field on Lead records is set to FALSE.
Super Round Robin's processing is very quick, and if this field is set to TRUE by default, SRR might have picked up a new Lead before the PDO flow even got a chance to process it via Record Validation and Duplicate Check first. This might lead to records being assigned and then immediately being taken away again because they turned out to be duplicates, which can be confusing for assignees.
