...
Requirement | User Story | Importance | Jira Issue | Notes | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | CRUD Processr Job | As an Admin, Agency users should be able to add a processr job to a campaign. They should be able to set a “label” for the processr job so they can see reference in reporting and logs etc Users should be able to delete a processr job to a campaign however before deleting the job validation will need to prompt before being removed. |
| ||||||||
| 2 | Configure Processr Job | As an Admin, Agency user they should be able to Configure a processr job on a campaign. Once the processr job has been added to a campaign they will be allowed to configure the job to allow them to change settings and mappings. |
|
|
| ||||||
| 3 | CRUD Label, Configure Score, Hard fail and Stage | As an Admin, Agency user they should be able to edit the table values on a processr job on a campaign. The user will be able to set the score to any numeric value and save. The user will be able to specify if hard-fail is yes or no. The user will be able to select from a drop-down the stage at which the processr job should run. |
| ||||||||
| 4 | Manage Processr Jobs (job Groups) | As an Admin, Agency user they should be able to add processr job(s) on a campaign to a processr job group. Once they have selected the jobs that they want to assign to a group this will then give them the option to name and set a score for the job group. After setting up the Job group, the user will be able to configure the settings to either be a value or a catch-all and along with being able to set a condition. |
| ||||||||
| 5 | Value-Based Routing |
User interaction and design
...