Target release | |
|---|---|
Epic | |
Document status | |
Document owner | |
Designer | |
Tech lead | |
Technical writers | |
QA |
Fill in project details in the table below. Type /date to quickly add the target release date, /jira to link to Jira epics or issues, and @mention functional owners to keep everyone on the same page.
|
The processr section on a campaign allows users to define the criteria (rules) in which a lead data record would be deemed as valid. Once the platform has decided if the lead data is valid it will then try and send the data to an external system such as a CRM.
Within the processr tab there will be the tabs below:
Pre-Processr: these are types of jobs that
QA: Here they can add multiple proccessr jobs ranging from data formatting checks and live contact validation to achieve their desired results.
Enrichment: These are jobs in which they can append enrichment data via external 3rd party services to the data
Integration: These processr jobs are around sending data externally from the platform typically in most instances this will be to a CRM or ESP platform.
Processr Functionality
Job Groups: Here you can apply scenarios to your processr jobs to run different jobs based on different data scenarios.
Value-Based Routing: Allows our customers to run different integration jobs based on a data field
List project goals and the metrics you'll use to judge its success
Goal | Metric |
|---|---|
e.g., Simplify the user experience | e.g., Customer satisfaction score increases |
List any assumptions you have about your users, technical constraints, or business goals (e.g., Most users will access this feature from a tablet)
Requirement | User Story | Importance | Jira Issue | Notes | |
|---|---|---|---|---|---|
| 1 | CRUD Processr Job | As an Admin, Agency & Creative Manager 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 & Creative Manager users 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 | Configure Score, Hard fail and Stage | As an Admin, Agency & Creative Manager users 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 & Creative Manager users 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 |
https://projects.invisionapp.com/d/main#/console/18086130/403166218/preview
Question | Answer | Date Answered |
|---|---|---|
e.g., How might we make users more aware of this feature? | e.g., We'll announce the feature with a blog post and a Summit presentation |
List the features discussed which are out of scope or might be revisited in a later release.