This commit improve event.type (Event Categories) model and views in order to ease event configuration through more detailed categories. The purpose is to be able to define categories holding default data for website, tickets, attendee mailing, ... Choosing a category on a new event takes those default values to help users creating finely-tuned events. Main configuration on event.type is * auto confirmation, replacing the old system-wide auto confirmation parameter * seats limitation * location: online events, timezone * communication: reply-to email address, twitter hashtag, automated mailing of attendees * ticketing * website parameters: display on website, display tracks, allow track proposal * question to attendees
26 lines
1.1 KiB
XML
26 lines
1.1 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<data noupdate="1">
|
|
<!-- notify all employees of module installation -->
|
|
<function model="mail.channel" name="message_post">
|
|
<value eval="[ref('mail.channel_all_employees')]"/>
|
|
<value>From the top menu Events, you can organize events, manage registrations, automate communication around your event and sell events through your quotations.</value>
|
|
<value>Module Events has been installed</value>
|
|
</function>
|
|
|
|
<!-- Event Mail Scheduler-->
|
|
<record model="ir.cron" forcecreate="True" id="event_mail_scheduler">
|
|
<field name="name">Event: Mail Scheduler</field>
|
|
<field name="model_id" ref="model_event_mail"/>
|
|
<field name="state">code</field>
|
|
<field name="code">model.run(True)</field>
|
|
<field name="user_id" ref="base.user_root"/>
|
|
<field name="interval_number">1</field>
|
|
<field name="interval_type">hours</field>
|
|
<field name="numbercall">-1</field>
|
|
<field name="doall" eval="False" />
|
|
</record>
|
|
|
|
</data>
|
|
</odoo>
|