Thibault Delavallée
f9993774f1
the access rules, notably about reading and creation. This allows by the way to remove the hack about the operation in context when subscribing users on a document. The new rules on create and read now include user_id, aka the owner of a note can always create (default value) and read its notes. Also removed an unnecessary field (current_partner_id), as it was buggy and unnecessary; view udpated accordingly. [IMP] mail: removed a hack introduced in saas-3 with the current orm operation in context to by-pass some access rules when subscribing someone on a document. bzr revid: tde@openerp.com-20140219111330-l3hw5324hvuikpjc
31 lines
1.2 KiB
XML
31 lines
1.2 KiB
XML
<?xml version="1.0"?>
|
|
<openerp>
|
|
<data>
|
|
<record id="note_note_rule_global" model="ir.rule">
|
|
<field name="name">Only followers can access a sticky notes</field>
|
|
<field name="model_id" ref="model_note_note"/>
|
|
<field name="domain_force">['|', ('user_id', '=', user.id), ('message_follower_ids', '=', user.partner_id.id)]</field>
|
|
<field name="global" eval="True"/>
|
|
<field name="perm_create" eval="False"/>
|
|
<field name="perm_unlink" eval="False"/>
|
|
</record>
|
|
|
|
<record id="note_note_create_unlink_global" model="ir.rule">
|
|
<field name="name">note: create / unlink: responsible</field>
|
|
<field name="model_id" ref="model_note_note"/>
|
|
<field name="domain_force">[('user_id', '=', user.id)]</field>
|
|
<field name="global" eval="True"/>
|
|
<field name="perm_write" eval="False"/>
|
|
<field name="perm_read" eval="False"/>
|
|
</record>
|
|
|
|
<record id="note_stage_rule_global" model="ir.rule">
|
|
<field name="name">Each user have his stage name</field>
|
|
<field name="model_id" ref="model_note_stage"/>
|
|
<field name="domain_force">['|',('user_id','=',False),('user_id','=',user.id)]</field>
|
|
<field name="global" eval="True"/>
|
|
</record>
|
|
|
|
</data>
|
|
</openerp>
|