# lead_rule Event Lead Rules * per attendee: create a lead for each registration; * per order: create a lead for a group of registrations; The last one is only available through interface if it is possible to register a group of attendees in one action (when event_sale or website_event are installed). Behavior itself is implemented directly in event_crm. Basically a group is either a list of registrations belonging to the same event and created in batch (website_event flow). With event_sale this definition will be improved to be based on sale_order. There are three options to trigger lead creation. We consider basically that lead quality increases if attendees confirmed or went to the event. Triggers * at attendee creation; * at attendee confirmation; * at attendee venue; This trigger defines when the rule will run. When a batch of registrations matches the rule trigger we filter them based on conditions and rules defines on event_lead_rule model. Heuristic is the * the rule is active; * if a filter is set: filter registrations based on this filter. This is done like a search, and filter is a domain; * if a company is set on the rule, it must match event's company. Note that multi-company rules apply on event_lead_rule; * if an event category it set, it must match; * if an event is set, it must match; * if both event and category are set, one of them must match (OR). If none of those are set, it is considered as OK; If conditions are met, leads are created with pre-filled informations defined on the rule (type, user_id, team_id). Contact information coming from the registrations are computed (customer, name, email, phone, mobile, contact_name). Note that all rules matching their conditions are applied. This means more than one lead can be created depending on the configuration. This is intended in order to give more freedom to the user using the automatic lead generation. ## Documentation Rule model for creating / updating leads from event registrations. - Catalog: `Odoo` - Schema: `event` - SPECIFICATIONS: OTHER POINTS - There are two types of lead creation: - allow therefore to run rules: - following: The data in this table is partitioned per value of the column. This is a read-only table. The Odoo API may not support changing the data or the Invantive SQL driver for Odoo does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Odoo API. ## Table Columns The columns of the table `lead_rule` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `active` | `boolean` | Active | ☐ | | | `company_id_label` | `string` | | ☐ | Restrict the trigger of this rule to events belonging to a specific company. If not set, no company restriction will be applied. | | `company_id` | `string` | | ☐ | Restrict the trigger of this rule to events belonging to a specific company. If not set, no company restriction will be applied. | | `create_date` | `datetime` | Created on | ☐ | | | `create_uid_label` | `string` | | ☐ | | | `create_uid` | `string` | | ☐ | | | `display_name` | `string` | Display Name | ☐ | | | `event_id_label` | `string` | | ☐ | Filter the attendees to include those of this specific event. If not set, no event restriction will be applied. | | `event_id` | `string` | | ☐ | Filter the attendees to include those of this specific event. If not set, no event restriction will be applied. | | `event_registration_filter` | `string` | Registrations Domain | ☐ | Filter the attendees that will or not generate leads. | | `event_type_ids` | `string` | | ☐ | Filter the attendees to include those of this specific event category. If not set, no event category restriction will be applied. | | `id` | `int32` | ID | ☐ | | | `lead_creation_basis` | `string` | Create | ☑ | Per Attendee : A Lead is created for each Attendee (B2C). Per Order : A single Lead is created per Ticket Batch/Sale Order (B2B) | | `lead_creation_trigger` | `string` | When | ☑ | Creation: at attendee creation; Confirmation: when attendee is confirmed, manually or automatically; Attended: when attendance is confirmed and registration set to done; | | `lead_ids` | `string` | | ☐ | | | `lead_sales_team_id_label` | `string` | | ☐ | Automatically assign the created leads to this Sales Team. | | `lead_sales_team_id` | `string` | | ☐ | Automatically assign the created leads to this Sales Team. | | `lead_tag_ids` | `string` | | ☐ | Automatically add these tags to the created leads. | | `lead_type` | `string` | Lead Type | ☑ | Default lead type when this rule is applied. | | `lead_user_id_label` | `string` | | ☐ | Automatically assign the created leads to this Salesperson. | | `lead_user_id` | `string` | | ☐ | Automatically assign the created leads to this Salesperson. | | `name` | `string` | Rule Name | ☑ | | | `write_date` | `datetime` | Last Updated on | ☐ | | | `write_uid_label` | `string` | | ☐ | | | `write_uid` | `string` | | ☐ | |