This is an old revision of the document!
Lime CRM layout
Certain fields needs to exist in LISA in order for the integration to work. If the fields or table names can't be changed in LISA due to other integrations, they can be changed in the integration configuration setup instead.
Mailing
Identified by tablename; mailing. Used to save mailings to campaigns and store the statistic links. All field should be Read only
| Field name | Required | Field type | Description |
|---|---|---|---|
| subject | Yes | Text field | The subject from the mailing (1024 characters) |
| campaign | Yes | relation: (1:n campaign-mailing) | Relation to the campaign, a campaign can have many mailings |
| statisticlink | Yes | Link field | Hidden field used to hold statistic link from Bizwizard (1024 characters) |
| sendoutlink | Yes | Link field | Hidden field used to hold send out link from Bizwizard, e.i the actual layout of the mail sent (1024 characters) |
| htmlstatisticlink | No | Html-tab | SQL-expression: [mailing].[statisticlink]. Displays the content of the statistic link |
| htmlsendoutlink | No | Html-tab | SQL-expression: [mailing].[sendoutlink]. Displays the content of the send out link |
| mailingid | Yes | Integer | The mailing id from Bizwizard, should be hidden |
| senddate | Yes | Datetime (only date) | The date when the mailing was done |
Recipient
Identified by table name; recipient. Used to store recipients connected to a certain mailing and store their mailing status (sent, opened, clicked and bounce). All fields should be read-only.
| Field name | Required | Field type | Description |
|---|---|---|---|
| person | Yes | relation: (1:n person-recipient) | Relation to the person, a person can have many recipients |
| mailing | Yes | relation: (1:n mailing-recipient) | Relation to the mailing, a mailing can have many recipients |
| sendoutstatus | Yes | Option list | Used to set status for the mailing. must contain correct option keys |
Field: sendoutstatus
Option keys:
- sent
- open
- clicked
- bounce
Marketing activity
Lime CRM marketing activity records are used for storing mailing lists and therefore a table having the Campaign label must exist. On the marketing activity table there must be three fields:
| Field name | Required | Field type | Description |
|---|---|---|---|
| name | Yes | Text field | text field used for finding campaigns in Bizwizard. |
| type | Yes | Option list | Used to filter out which campaigns should be available in Bizwizard. |
| campaignstatus | Yes | Option list | Used to filter out which campaigns should be available in Bizwizard. |
| participant | Yes | Relation (n-1 participant-campaign) | The participants are thoses who will get the sendout |
| mailing | Yes | Relation (n-1 mailing-campaign) | The mailings sent from Bizwizard |
Person
Identified by the table having the Person table label. The Bizwizard Integration will look for the fields:
| Field name | Required | Field type | Description |
|---|---|---|---|
| firstname | Yes | Text field | Firstname |
| lastname | Yes | Text field | Lastname |
| Yes | Link field | The email to the person IMPORTANT: Used as key | |
| totaloptout | Yes | Checkbox | Read only that is controlled from Bizwizard to mark up total opt-outs |
| emailhardbounce | Yes | Checkbox | Read Only that is controlled from Bizwizard to mark up hard bounces (“error” in e-mail address) |
| recipient | Yes | Relation (n-1 recipient-subscriber) | Relation to recipient (middle-object between mailing and person) |
Company
Identified by the table having the Company table label. The Bizwizard Integration will look for the fields:
| Field name | Required | Field type | Description |
|---|---|---|---|
| name | Yes | Text field | Name of the company |
| coworker | Yes | realtion (1-n coworker-company) | The coworker responsible for the customer |