What does it do?
This job’s function is to identify if a lead has a duplicate value across selected fields, from a list of set values. Eg If the same value from the defined list is found within the configured fields this will be flagged as a duplicate.
Actions | Description | Acceptance Criteria | |
|---|---|---|---|
| 1 | fields | From the drop-down menu, you can select the fields you would like this check to run against. The user can add as many fields as they choose. | The user can add multiple fields for the processr job to reference by clicking add |
| 2 | values | From the drop-down menu, you can select yes or no | The user can add multiple values for the processr job to reference (user can add blank values if for one field in non mandatory) by clicking add |
| 3 | case_sensitive | From the drop-down menu, you can select yes or no | The user can select yes or no (if the user select no the job will not be case sensitive) |
What use case?
Content Syndication
Why would clients find this useful?
This helps users prevent leads from having the same value across multiple fields.
Key Talking points:
If the client wants to avoid duplicate values over multiple fields
It gives more control over multi-touch leads
An example of how it would be implemented?
if the user is capturing data in three fields called asset_1, asset_2 and asset_3 and they have a list of values that can be populated in these three fields eg Dr Strange, The Hulk and Spiderman this job will prevent the values from the defined list from repeating more than once.
Set-Up
Scenarios | |
|---|---|
A value was found no in the list eg Tony Stark |  |
Case_sensative setting being set to yes, if this was no the lead would of passed |  |
Ths shows the acceptance of a blank setting (non mandatory field) |  |
The same value being repepted multiple times |  |
The shows the accepted outcome |  |
If the lead does not have the field that the job is configured to eg: in the settings i put the option 'value'  |  |