Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 6 Next »

Target release

Epic

https://convertr.atlassian.net/browse/PM-119

Document status

DRAFT

Document owner

Adam Carter

Designer

Tech lead

Technical writers

QA

Objective

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

Success metrics

Goal

Metric

Assumptions

Requirements

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.

HIGH

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, Score, Hard fail and Stage

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

5

Value-Based Routing

User interaction and design

https://projects.invisionapp.com/d/main#/console/18086130/403166218/preview

Open Questions

Question

Answer

Date Answered

Out of Scope

  • No labels