openerp-india team mailing list archive

["Stefan Rijnhart \(Therp\)" <1070884@xxxxxxxxxxxxxxxxxx>]

Hi Daniel,

if both 'pre' write and 'post' write have their separate purposes, then
maybe OpenERP should eventually allow marking the rules for either of
them, so having perm_pre_write and perm_post_write flags instead of just
perm_write.

For now I think the inconsistency between not allowing the user to
create a resource with property A but still allowing to modify an
existing resource to the same result is a pretty obvious defect that
should be addressed.

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Server.
https://bugs.launchpad.net/bugs/1070884

Title:
  ir_rule should apply to the result of a Model.write()

Status in OpenERP Server:
  Fix Committed
Status in Therp Backports:
  Fix Committed

Bug description:
  Currently in OpenERP 6.1 and trunk the record rules are applied at
  write time only before the resource is written. This is inconsistent
  with creating resources, as in that case the record rules are applied
  at the results.

  For instance, we have applied a record rule that restricts HR officers
  from writing their own record (or their contracts). Under the current
  behaviour, they can still create a new employee with their own user
  associated with it (but they cannot delete it).

  I think that the rule should apply to the resources before
  modification as well as after the modification.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-server/+bug/1070884/+subscriptions