Commit 26956853 authored by Kazuhiko Shiozaki's avatar Kazuhiko Shiozaki

no longer set solver category in simulation movements, because one simulation...

no longer set solver category in simulation movements, because one simulation movements can be related to several solver decisions.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@33571 20353a03-c40f-0410-a6d1-a30d3c3de9de
parent 03c8dd20
...@@ -217,9 +217,6 @@ class SolverProcess(XMLObject, ActiveProcess): ...@@ -217,9 +217,6 @@ class SolverProcess(XMLObject, ActiveProcess):
new_decision = self.newContent(portal_type='Solver Decision') new_decision = self.newContent(portal_type='Solver Decision')
new_decision._setDeliveryList(solver_decision_key[1]) new_decision._setDeliveryList(solver_decision_key[1])
new_decision._setCausality(solver_decision_key[0]) new_decision._setCausality(solver_decision_key[0])
for simulation_movement in movement_dict.keys():
simulation_movement.setSolverValue(new_decision)
# No need to set application_list or....?
def _generateRandomId(self): def _generateRandomId(self):
# call ActiveProcess._generateRandomId() explicitly otherwise # call ActiveProcess._generateRandomId() explicitly otherwise
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment