Difference between revisions of "Understanding the bxp Form structure"
Philip Lacey (talk | contribs) (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...") |
Philip Lacey (talk | contribs) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 72: | Line 72: | ||
|- | |- | ||
| 1 || 1 || 2014-01-01 13:00:00 || 2014-01-01 13:05:00 || Agent 1 || Interested || Wants more info but later | | 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 | | 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 | | 3 || 1 || 2014-01-02 10:05:00 || 2014-01-02 10:12:23 || Agent 1 || Sale || Called and sold service | ||
|- | |- | ||
| Line 82: | Line 84: | ||
Each CDA may have anything from none to many CCLs. | Each CDA may have anything from none to many CCLs. | ||
| + | |||
| + | |||
| + | |||
| + | = Form System Fields = | ||
| + | |||
| + | |||
| + | If you want to see the structure of the CDA table you can use Field Mapping. [[Understanding_Field_Mapping]] | ||
| + | |||
| + | |||
| + | When a form is built it has a number of system fields automatically added. X will be the unique Form Id. | ||
| + | |||
| + | * intCDA_X_Id : The unique ID for each CDA record | ||
| + | * strCDA_X_ : Future use, used in various different ways. | ||
| + | * strCDA_X_Status : The last outcome used on this CDA | ||
| + | * strCDA_X_NoOfAttempts : The total number of CCLs that have been logged against this CDA | ||
| + | * strCDA_X_StaffId : The last staff Id to interact with this record | ||
| + | * strCDA_X_LastDateTime : The last date and time this record was interacted with | ||
| + | |||
| + | |||
| + | You will also have strCDA_X_field_Y_Z fields for every question you add to your form. | ||
| + | |||
[[Category:Module Specific:Form Management]] | [[Category:Module Specific:Form Management]] | ||
[[Category:Topic:Key Concept]] | [[Category:Topic:Key Concept]] | ||
Latest revision as of 15:57, 8 March 2016
1 Overview
This article comes from CC-1-3 Introduction to the Blended Form Structure
2 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 
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
| 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:
| 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.
3 Form System Fields
If you want to see the structure of the CDA table you can use Field Mapping. Understanding_Field_Mapping
When a form is built it has a number of system fields automatically added. X will be the unique Form Id.
- intCDA_X_Id : The unique ID for each CDA record
- strCDA_X_ : Future use, used in various different ways.
- strCDA_X_Status : The last outcome used on this CDA
- strCDA_X_NoOfAttempts : The total number of CCLs that have been logged against this CDA
- strCDA_X_StaffId : The last staff Id to interact with this record
- strCDA_X_LastDateTime : The last date and time this record was interacted with
You will also have strCDA_X_field_Y_Z fields for every question you add to your form.