Navigation: Schema: event > Tables

lead_rule

Event Lead Rules

Catalog: Odoo

Schema: event

Documentation:

Rule model for creating / updating leads from event registrations.

SPECIFICATIONS: CREATION TYPE

There are two types of lead creation:

* 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.

SPECIFICATIONS: CREATION TRIGGERS

There are three options to trigger lead creation. We consider basically that

lead quality increases if attendees confirmed or went to the event. Triggers

allow therefore to run rules:

* at attendee creation;

* at attendee confirmation;

* at attendee venue;

This trigger defines when the rule will run.

SPECIFICATIONS: FILTERING REGISTRATIONS

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

following:

* 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).

SPECIFICATIONS: OTHER POINTS

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.

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		☐

01-03-2023 15:29 Version 22.1.135-BETA+3826

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

Please enable JavaScript to view this site.

Odoo API Data Model

lead_rule

Table Columns

Important Safety and Usage Information