Anonymous, bureaucrat, administrator
7,528
edits
Changes
From All n One's bxp software Wixi
Created page with "= Overview = This article comes from CC-1-3 Introduction to the Blended Form Structure = Forms = Data in bxp is stored in a collection of database tables which can be r..."
= Overview =
This article comes from CC-1-3 Introduction to the Blended Form Structure
= Forms =
Data in bxp is stored in a collection of database tables which can be referred to as a campaign or database but is called a '''Form''' by All n One. Every form has its own unique id known as a '''Form Id'''.
The data in these forms is managed through a number of modules:
* Inbound Contact
* Outbound Contact
* Case Management
* Testing Centre
* Quality Assurance
* Survey
The management of all forms is done through the '''Form Management''' [[File:038.png]] module. Each form has its own unique Id which is represented as X in this article. In every form in bxp, there are two key separate elements: '''Records''' and '''Contacts'''.
A record is a set of data for one element, like a customer. You can store as many pieces of information ('''fields''') as you like for one record. Fields in a record usually contain:
* Id A unique reference for the customer
* Firstname The firstname of the customer
* Surname The surname of the customer
* Home Phone The home phone number for customer
* Work Phone The work contact phone number for the customer
* Mobile The mobile phone number for the customer
* Email The primary contact email address for the customer
Looking at the following table of records
{| class="wikitable"
! Id
! Firstname
! Surname
! Home Phone
! Work Phone
! Mobile
! Email
|-
| 1 || Nick || Wheeler || 01 1234567 || 01 4294000 || 353871231231 || nick.wheeler@allnone.ie
|-
| 2 || Chris || Thomson || 01 2345678 || 01 4294000 || 353871231232 || chris.thomson@allnone.ie
|-
| 3 || Philip || Lacey || 01 3456789 || 01 4294000 || 353861231230 || philip.lacey@allnone.ie
|-
|}
Each line of information is a record. bxp builds a table to store these records. A table can also be considered like an Excel spreadsheet. Each row in the spreadsheet is a record.
bxp calls these records '''Campaign DAta''' records ('''CDA''').
bxp can also capture contacts with these records. Each contact with a customer is stored in a separate table just for contacts. The contact is linked back to the appropriate record by its CDA Id. So for a sample of three contacts with Nick Wheeler, the contacts table might contain:
{| class="wikitable"
! Id
! CDA_Id
! Start
! End
! Agent
! Outcome
! Comment
|-
| 1 || 1 || 2014-01-01 13:00:00 || 2014-01-01 13:05:00 || Agent 1 || Interested || Wants more info but later
| 2 || 1 || 2014-01-01 14:30:00 || 2014-01-01 14:36:00 || Agent 2 || Call back || Rang back and gave info
| 3 || 1 || 2014-01-02 10:05:00 || 2014-01-02 10:12:23 || Agent 1 || Sale || Called and sold service
|-
|}
bxp calls these records '''Campaign CaLls''' records ('''CCL''').
Each CDA may have anything from none to many CCLs.
[[Category:Module Specific:Form Management]]
[[Category:Topic:Key Concept]]
This article comes from CC-1-3 Introduction to the Blended Form Structure
= Forms =
Data in bxp is stored in a collection of database tables which can be referred to as a campaign or database but is called a '''Form''' by All n One. Every form has its own unique id known as a '''Form Id'''.
The data in these forms is managed through a number of modules:
* Inbound Contact
* Outbound Contact
* Case Management
* Testing Centre
* Quality Assurance
* Survey
The management of all forms is done through the '''Form Management''' [[File:038.png]] module. Each form has its own unique Id which is represented as X in this article. In every form in bxp, there are two key separate elements: '''Records''' and '''Contacts'''.
A record is a set of data for one element, like a customer. You can store as many pieces of information ('''fields''') as you like for one record. Fields in a record usually contain:
* Id A unique reference for the customer
* Firstname The firstname of the customer
* Surname The surname of the customer
* Home Phone The home phone number for customer
* Work Phone The work contact phone number for the customer
* Mobile The mobile phone number for the customer
* Email The primary contact email address for the customer
Looking at the following table of records
{| class="wikitable"
! Id
! Firstname
! Surname
! Home Phone
! Work Phone
! Mobile
|-
| 1 || Nick || Wheeler || 01 1234567 || 01 4294000 || 353871231231 || nick.wheeler@allnone.ie
|-
| 2 || Chris || Thomson || 01 2345678 || 01 4294000 || 353871231232 || chris.thomson@allnone.ie
|-
| 3 || Philip || Lacey || 01 3456789 || 01 4294000 || 353861231230 || philip.lacey@allnone.ie
|-
|}
Each line of information is a record. bxp builds a table to store these records. A table can also be considered like an Excel spreadsheet. Each row in the spreadsheet is a record.
bxp calls these records '''Campaign DAta''' records ('''CDA''').
bxp can also capture contacts with these records. Each contact with a customer is stored in a separate table just for contacts. The contact is linked back to the appropriate record by its CDA Id. So for a sample of three contacts with Nick Wheeler, the contacts table might contain:
{| class="wikitable"
! Id
! CDA_Id
! Start
! End
! Agent
! Outcome
! Comment
|-
| 1 || 1 || 2014-01-01 13:00:00 || 2014-01-01 13:05:00 || Agent 1 || Interested || Wants more info but later
| 2 || 1 || 2014-01-01 14:30:00 || 2014-01-01 14:36:00 || Agent 2 || Call back || Rang back and gave info
| 3 || 1 || 2014-01-02 10:05:00 || 2014-01-02 10:12:23 || Agent 1 || Sale || Called and sold service
|-
|}
bxp calls these records '''Campaign CaLls''' records ('''CCL''').
Each CDA may have anything from none to many CCLs.
[[Category:Module Specific:Form Management]]
[[Category:Topic:Key Concept]]
