An error occurred fetching the project authors.
- 26 Jan, 2013 1 commit
-
-
Julien Muchembled authored
Use of catalog to get related simulation movements from delivery lines/cells is unreliable. Until now, for any new code written for simulation, we often had to be careful not to call getDeliveryRelatedValueList too early, usually by deferring code to activities with complicated dependencies. Race conditions are difficult to avoid by developping this way, because for a given delivery, there are potentially so many events that happen at the same time, involving: - simulation, amongst causality, expand, building, solving (including split) - alarms, user actions, external interfaces, chains of activities - several related deliveries and simulation trees This commit enables ZODB-indexing of related documents for 'delivery' base category, making getDeliveryRelatedValueList safe and fixing unlink of deleted delivery lines/cells. Existing activity dependencies are left unchanged because builders only uses catalog and local building needs to find all simulation movements.
-
- 18 Dec, 2012 1 commit
-
-
Julien Muchembled authored
-
- 17 Dec, 2012 2 commits
-
-
Julien Muchembled authored
-
Julien Muchembled authored
-
- 03 Oct, 2012 1 commit
-
-
Julien Muchembled authored
All interactions and activity tags are reviewed to fix bugs like duplicated root applied rules, and also reduces the amount of duplicated/useless work, e.g: - Simulation trees are not expanded anymore when simulated objects are modified. - 'expand' activities are merged (i.e. dropped) with any other 'expand' activity for an ancestor. New implementation exposes new API that hides much complexity to the developper about activity dependencies. By default, expand() now automatically defers any work if the current transaction takes too long time. This method also gains a parameter to explicitely choose when to expand, which is often important in unit tests or solvers. In particular, when postponing work, it takes care of setting proper activity dependencies. - If you have any code requiring to expand everything immediately, you'll have to replace 'expand()' by 'expand(expand_policy="immediate")'. - On the contrary, you should replace any 'activate().expand()' by 'expand(expand_policy="deferred")'. expand() still accepts activity parameters for any extra needs. In causality workflow, 'building' state is clarified and now means « delivery may diverge but we can't know now ». A delivery remains in draft as long as it does not contain any movement built from simulation. After init/clone/builder/etc. scripts used to call 'startBuilding' & 'updateCausalityState': this calls must be removed since only SimulatedDeliveryBuilder should take care of move to 'building' state and workflows now triggers 'updateCausalityState'. Disguised interactions have been unhardcoded and either deleted, or moved to appropriate interaction workflows, which have been reorganized. Those that triggers update of portal_workflow can be easily customized or disabled. New API: - updateSimulation() on deliveries and subscription items. It takes care of creating root applied rule, expanding and reindexing parts of simulation trees. It somehow replaces: - Delivery_updateSimulation - Delivery_updateAppliedRule - Delivery.applyToDeliveryRelatedMovement - Delivery.updateAppliedRule - Delivery.expand - Delivery.expandRuleRelatedToMovement - SubscriptionItem.expand - SubscriptionItem.updateAppliedRule - Delivery.localBuild() is the new way to do local building and replaces Delivery_expandAndBuild. Private method Delivery._localBuild replaces Delivery_buildOnComposedDocument. - Simulation Movements that are being built by a builder are reindexed with the following tag: 'built:<delivery_path>'. Any after_path_and_method_id dependency against 'related_simulation_movement_path_list' and reindexing methods should be replaced by this after_tag. After builder scripts used to confirm the delivery in a separate activity, which was useless.
-
- 15 May, 2012 1 commit
-
-
Julien Muchembled authored
This is a followup to commit 8995b645 ("always start transactions with begin() and make tic() commit automatically"): there is now no need to use self.stepTic() instead of self.tic()
-
- 11 May, 2012 1 commit
-
-
Julien Muchembled authored
-
- 29 Mar, 2012 1 commit
-
-
Rafael Monnerat authored
- Solvers were moved to erp5_configurator_standard_solver - trade related code and rules to erp5_configurator_standard_trade_template - accounting related code and rules to erp5_configurator_standard_accounting_template - invoicing related code and rules to erp5_configurator_standard_invoicing_template Code were moved and splited to several diferent business templates. The rules and related code should be used only as template.
-
- 12 Dec, 2011 1 commit
-
-
Julien Muchembled authored
- Stop calling rule.test() again. - For Applied Rule objects that don't specialise to an applicable rule: - do not expand built ones; - and delete others (e.g. if a new rule matches, replace it).
-
- 31 Oct, 2011 1 commit
-
-
Leonardo Rochael Almeida authored
Rules should now contain all predicates necessary for matching the right simulation movements. Which they now can do since they all have "Predicate" tabs now. (partially revert 5c2c470f)
-
- 18 Oct, 2011 1 commit
-
-
Leonardo Rochael Almeida authored
-
- 17 Oct, 2011 2 commits
-
-
Leonardo Rochael Almeida authored
And add a test checking this in portal_rules
-
Leonardo Rochael Almeida authored
-
- 13 Oct, 2011 1 commit
-
-
Leonardo Rochael Almeida authored
Both for _identity_criterion and _range_criterion Add tests showing direct criteria specification in predicate scripts And rule tests to match on simulation movements, since this is what rules match most of the time.
-
- 19 Apr, 2011 1 commit
-
-
Leonardo Rochael Almeida authored
add trade_phase predicates to rules and check that already applied rules are not rejected just because of that git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@45578 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 09 Nov, 2010 1 commit
-
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@40112 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 07 Nov, 2010 1 commit
-
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@40004 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 07 Oct, 2010 1 commit
-
-
Yusei Tahara authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@38941 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 13 Aug, 2010 1 commit
-
-
Yoshinori Okuji authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@37782 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 13 Oct, 2009 1 commit
-
-
Łukasz Nowak authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@29606 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 29 Jun, 2009 1 commit
-
-
Julien Muchembled authored
Fix unit tests of ERP5 Product so that they don't call unsupported workflow methods. Transitions of the following workflows were not considered: * amortisation_transaction_causality_workflow * event_workflow * processing_status_workflow * publication_workflow git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@27822 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 12 May, 2009 1 commit
-
-
Jérome Perrin authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26926 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 07 Apr, 2009 1 commit
-
-
Kazuhiko Shiozaki authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26319 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 26 Jan, 2009 1 commit
-
-
Kazuhiko Shiozaki authored
Sale Packing List in afterSetUp(). git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@25299 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 06 Dec, 2007 1 commit
-
-
Jérome Perrin authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@18071 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 23 Nov, 2007 1 commit
-
-
Alexandre Boeglin authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@17768 20353a03-c40f-0410-a6d1-a30d3c3de9de
-