[Erp5-report] r38536 tatuya - /erp5/trunk/products/ERP5/Document/
nobody at svn.erp5.org
nobody at svn.erp5.org
Wed Sep 22 10:00:44 CEST 2010
Author: tatuya
Date: Wed Sep 22 10:00:43 2010
New Revision: 38536
URL: http://svn.erp5.org?rev=38536&view=rev
Log:
Make it possible to decide updating existing document or not with the update_always flag.
Modified:
erp5/trunk/products/ERP5/Document/PropertyGroupingMovementGroup.py
Modified: erp5/trunk/products/ERP5/Document/PropertyGroupingMovementGroup.py
URL: http://svn.erp5.org/erp5/trunk/products/ERP5/Document/PropertyGroupingMovementGroup.py?rev=38536&r1=38535&r2=38536&view=diff
==============================================================================
--- erp5/trunk/products/ERP5/Document/PropertyGroupingMovementGroup.py [utf8] (original)
+++ erp5/trunk/products/ERP5/Document/PropertyGroupingMovementGroup.py [utf8] Wed Sep 22 10:00:43 2010
@@ -36,10 +36,12 @@ class PropertyGroupingMovementGroup(Move
portal_type = 'Property Grouping Movement Group'
def test(self, document, property_dict, **kw):
- # We always separate the movements from the exsiting document, because we
- # did not assign the properties into the document thanks to this movement group.
+ # We did not assign the properties into the document thanks to this movement group.
# Therefore their is no way to compare the properties between the document
# and the movements. In other words, they are always different.
+ # So, we only check the update_always flag on the movement group setting here.
+ if self.isUpdateAlways():
+ return True, {}
return False, {}
def _separate(self, movement_list):
More information about the Erp5-report
mailing list