...
Actions | Description | Acceptance Criteria | |
|---|---|---|---|
| 1 | fields | From the drop-down menu, As a user you can select specify the fields you would like this check to run against. The user can add as many fields as they choose and select from drop-down menu of available fields. | The user can add multiple fields for the processr job to reference by clicking add |
| 2 | valuesFrom | the drop-down menu, you can select yes or noAs a user you can add the values you would like this check to run against. The user can add as many values as they choose. | 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) |
...
An example of how it would be implemented?
if 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 not found no in the list eg Tony Stark |  |
Case_sensative setting being set to yes‘yes’, if this was no set to ‘no’ the lead would of passed. |  |
Ths This shows the acceptance of a blank setting (non mandatory field) |  |
The same value being repepted repeated multiple times |   |
The This shows the accepted outcome |  |
If the lead does not have the field that the job is configured to eg: in In the settings i put if users puts the option 'value'  |  |