...
Validation lists will tend to have thousands of records if not more.
Requirements
Requirement | User Story | Importance | Jira Issue | Notes | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|
1 | CRUD global validation lists | As an admin or agency user, I should be able to create, edit and delete validation lists on a global level. I should be able to create many validation lists globally. I should be able to set a “name” for my validation list so I can determine it’s contents. |
| ||||||||
2 | CRUD advertiser validation lists | As an admin or agency user, I should be able to create, edit and delete validation lists specifically to an Advertiser within the system. As per the global lists, I should be able to create many validations lists for a single advertiser. I should be able to set a “name” for my validation list so I can determine it’s contents |
|
|
| ||||||
3 | Allow advertisers to create “Private” validation lists | As an Advertiser user, I should be able to create my own validation list and mark it as private. The role of the “private” validation list is to allow the advertiser to upload potentially sensitive information without exposing it to Agency or Publisher user types. Admin + Super Admin users should still be able to see private validations lists. |
| ||||||||
4 | Validation List Processr Job | As a user that sets up or manages a campaign, I would like to be able to cross reference a lead field value against the values of my validation list. I should be able to decide whether to perform an exact match on the values or use a partial match. I should also be able to choose whether matching a value is either a good thing or bad thing and pass / fail accordingly. I should also be able to configure a field name which contains multiple values and ensure they are all in a single validation list. For example I might have a field of I should also be able to choose whether to check the list strictly or loosely, using case sensitivity. Finally, I should be able to optionally bypass the check if I have a blank|empty value for my chosen field. This would be for us to handle fields that are optional, but if populated check against the validation lists values. |
| ||||||||
5 | Make validation lists visible to Publishers | As a publisher user, it would be useful for me to be able to download the contents of a validation list so I can ensure I am meeting the requirements of the campaign. As an agency user, I should be able to choose which validation lists to show to publishers. I should not be able to expose private validation lists. |
| ||||||||
6 | Import values using CSV file | As a user of the validation lists feature, I would expect to be able to import large |
CSV files of values for a validation list - this should be available for both adding and editing validation lists. I would also expect to have some sort of template or guide as to what format to import the values in. | |||||
7 | Validation on Deletion | As an admin or agency user, when trying to delete a validation list the platform will prompt for validation confirming that validation isn't assigned on and campaigns. If so the validation list will need to be removed from a campaign before you can delete the validation list. |
User interaction and design
Open Questions
Question | Answer | Date Answered |
---|---|---|
Out of Scope
In the future I would like to replace the legacy Telephone, Email and Name suppression with pre-built validation lists.