now aggregation is done in applied rule level.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31479 20353a03-c40f-0410-a6d1-a30d3c3de9de

product/ERP5/Document/NewOrderRule.py

@@ -129,7 +129,7 @@ class NewOrderRule(Rule):
     return (movement.getSource() is None or movement.getDestination() is None)
 
 class OrderRuleMovementGenerator(object):
-  def getAggregatedMovementList(self, context, movement_list=None,
+  def getGeneratedMovementList(self, context, movement_list=None,
                                 rounding=False):
     """
     Input movement list comes from order

product/ERP5/mixin/movement_collection_updater.py

@@ -66,7 +66,7 @@ class MovementCollectionUpdaterMixin:
     """
     # We suppose here that we have an IMovementCollection in hand
     decision_movement_list = context.getMovementList()
-    prevision_movement_list = movement_generator.getAggregatedMovementList(
+    prevision_movement_list = movement_generator.getGeneratedMovementList(
       self._getMovementGeneratorContext(context),
       movement_list=self._getMovementGeneratorMovementList(), rounding=rounding)