[Erp5-report] r33735 kazuhiko - /erp5/trunk/products/ERP5/Document/SolverProcess.py

[nobody at svn.erp5.org]

Author: kazuhiko
Date: Mon Mar 15 17:02:05 2010
New Revision: 33735

URL: http://svn.erp5.org?rev=33735&view=rev
Log:
revert r33571 and support multiple solver values in a simulation movement.

Modified:
    erp5/trunk/products/ERP5/Document/SolverProcess.py

Modified: erp5/trunk/products/ERP5/Document/SolverProcess.py
URL: http://svn.erp5.org/erp5/trunk/products/ERP5/Document/SolverProcess.py?rev=33735&r1=33734&r2=33735&view=diff
==============================================================================
--- erp5/trunk/products/ERP5/Document/SolverProcess.py [utf8] (original)
+++ erp5/trunk/products/ERP5/Document/SolverProcess.py [utf8] Mon Mar 15 17:02:05 2010
@@ -228,6 +228,9 @@
           new_decision = self.newContent(portal_type='Solver Decision')
         new_decision._setDeliveryList(solver_decision_key[1])
         new_decision._setCausality(solver_decision_key[0])
+        for simulation_movement in movement_dict.keys():
+          simulation_movement.setSolverValueList(
+            simulation_movement.getSolverValueList() + [new_decision])
     # XXX what should we do for non-matched existing solver decisions?
     # do we need to cancel them by using an appropriate workflow?