auto=True reports are looked up in the database for each rendering, so they do
no have to be in the report registry any longer.
auto=False reports will register themselves but at this point
they can be updated to use the new `parser` XML attribute.
bzr revid: vmt@openerp.com-20130322153955-s6nyux2pyez6c01w
This is needed so the uninstall process can simply go through
the installed data by using the ir_model_data entries in reverse
order (when ordered by IDs), so that parents are deleted before
children.
bzr revid: vmt@openerp.com-20130321133202-igea1vxlszfpk6pe
- the re-raising of exceptions ignored the "legal" exceptions
(the one used to early abort RPC calls and generate pop-ups)
- re-raising the exception was attempting to re-use the original
exception type but it does not always take only one argument
so it was breaking.
lp bug: https://launchpad.net/bugs/1146256 fixed
bzr revid: vmt@openerp.com-20130320132238-qzo3jptww59ndlch
mail_mail
- added recipient_ids field, that holds specific recipients in addition to email_to; this field replace the recipient_ids parameter of mail_mail.send(), allowing to re-send failed emails, or at least store the whole mail information about recipients,
- updated form view to add some missing fields in the view,
mail_message
- added 'reply_to' field, that holds specific reply_to value, before passing it to the created email notifications,
mail_compose_message
- added 'post' boolean field: whether the message will be posted on the document (using active_model_pool.message_post()), or if it should only be an email (using mail_mail.create()),
- added 'notify' boolean field: if the message is posted on the document, tells whether the followers should be notified of the message,
- added 'same_thread' boolean field: if not set, a custom reply_to will be used and the automatic thread routing in message_process will be py-passed,
email_template
- renamed 'email_recipients' field into 'partner_to' (more coherent: email_to is a list of emails, partner_to is a list of partner ids),
- added default template on res.partner, setting partner_to as obj.id,
- moving mass mailing action from mail to email_template, that now uses the previous template,
mail_compose_message in email_template
- added partner_to, email_to and email_cc to be able to use those fields, that exist on the template, in the wizard
crm
- updated basic lead/opportunity template, setting partner_to as obj.partner_id.id, or email_to as obj.email_from
- added mass mailing action for lead/opportunity that uses the previous template
bzr revid: tde@openerp.com-20130319095505-efv0mdzq2fnwnila
This is not only dangerous but also
completely inconsistent with the other
db management screens. It also represents
little improvement in terms of usability
for first-time users, since the password
is now mentioned on the comment just above
the field.
bzr revid: odo@openerp.com-20130318155618-z9s2izahnv1j2no6
Quick Create:
- [ADD] in context of 'user_id' fields the xml_ids of necessary groups,
Invite:
- [ADD] added send_mail boolean field on invite wizard, allowing to avoid sending emails when inviting someone as a follower on the document,
- [IMP] notification and invite signature: improved signature (now including: sender name, company name as a link to the company website); invite message and subject improved, small code re-organization
Misc:
- [IMP] sheet tags added in various form views in HR
bzr revid: tde@openerp.com-20130318121439-xyl34r9tdut6t19c
Example of use : <field name="user_id" string="Project Manager" context="{'default_groups_ref': ['base.group_user', 'project.group_project_manager']}"/> will add Employee (base.group_user) and Project Manager (project.group_project_manager) groups, as well as implied groups.
res_users:
- [add] added support of key in context of default_get. It contains a list of xml_ids of user groups; those groups, if found, are added to the newly created user,
- [ref] refactored simplified (quick create) view that is now more like a contact card, with login and email required because of the login email that will be send to the user
bzr revid: tde@openerp.com-20130318120905-1w9xpoyppnj62wlj