An error occurred fetching the project authors.
- 22 Apr, 2016 2 commits
-
-
Julien Muchembled authored
-
Sebastien Robin authored
This allows to have a nice default behavior for isDeletable without the need to bother which arguments we can pass. Also, make isDeletable of simulation movement supporting keyword arguments to avoid failures when generic action checking isDeletable is called
-
- 12 Jan, 2016 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 13 Nov, 2015 1 commit
-
-
Sebastien Robin authored
This mapping lack possibility of customization. We should later use a few getPortalSomethingStateList to replace this hardcoded mapping
-
- 02 Oct, 2015 1 commit
-
-
Sebastien Robin authored
Remove broken concept of Mapping Properties that was used on legacy simulation. We do not want to use this concept any more, any mapping should be done by rule themself. Removing mapping properties leads to more generic concepts and much simpler code. With legacy simulation, in case of returned sale packing list (in case we want to invoice in same sale invoice usual sale packing list and returned sale packing list) : AR (delivering_rule): -> SM (source/A, destination/B) -> AR (invoicing_rule, having mapped_property mapping source to destination and vice versa) -> SM (source/A, destination/B) builders and solvers where doing sm.getMappedProperty('source') which was equivalent to sm.getProperty('destination'), thus the mapping was done in live time Now in such case, we should implement mapping directly at rule level, and this should give: AR (delivering_rule): -> SM (source/A, destination/B) -> AR (invoicing_rule, reversing source and destination) -> SM (source/B, destination/A) here we directly have properties we wish, no need of hacks on builders and solvers
-
- 16 Oct, 2014 1 commit
-
-
Julien Muchembled authored
-
- 04 Sep, 2014 1 commit
-
-
Gabriel Monnerat authored
-
- 27 Aug, 2014 1 commit
-
-
Jérome Perrin authored
some projects uses such states in custom workflows
-
- 23 Jan, 2014 1 commit
-
-
Julien Muchembled authored
Simulation Movements use 'causality' to link to different portal types: - Business Link - Trade Model Path - amount generator line/cell Only Business Links implement getCompletedStateList.
-
- 16 Sep, 2013 1 commit
-
-
Jérome Perrin 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.
-
- 28 Jun, 2012 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 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).
-
- 07 Dec, 2011 1 commit
-
-
Julien Muchembled authored
-
- 31 Oct, 2011 2 commits
-
-
Leonardo Rochael Almeida authored
Don't even search for future trade phases.
-
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)
-
- 01 Aug, 2011 1 commit
-
-
Julien Muchembled authored
-
- 04 May, 2011 1 commit
-
-
Jérome Perrin authored
if a simulation movment has been explicitly marked as frozen, use this and not the info from business process git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@45812 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 19 Apr, 2011 1 commit
-
-
Leonardo Rochael Almeida authored
Make sure to check already applied rules against simulation movements with successor trade phases, just like was done to search for them in the first place git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@45577 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 13 Apr, 2011 1 commit
-
-
Sebastien Robin authored
to a particular trade phase category, so it was looking at business link of business process not all related to this particular simulation movement. So use asComposedDocument in order to get good list of business links * add comments about undocumented and untested code git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@45361 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 08 Apr, 2011 1 commit
-
-
Leonardo Rochael Almeida authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@45214 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 07 Apr, 2011 1 commit
-
-
Leonardo Rochael Almeida authored
Use Business Link causality to guess future trade_phases for Simulation Movement, removing the need for complex test scripts on portal rules git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@45191 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 14 Mar, 2011 3 commits
-
-
Jérome Perrin authored
Introduce a new interface expandable_item which extends expandable and add this functionality, and provides default implementation that maybe have to be extended for some specific subscription items usages. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@44254 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
Jérome Perrin authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@44229 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
Jérome Perrin authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@44228 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 12 Jan, 2011 1 commit
-
-
Julien Muchembled authored
- delaying 'updateCausalityState' instead of 'calculate' - make sure 'updateCausalityState' depends on all related simulation movements - do not process 'updateCausalityState' as long as there remains 'Delivery_calculate' activities This fixes r39050 ("fix an error that calculate may be called too early before a new simulation movement is indexed."). git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42258 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 21 Dec, 2010 1 commit
-
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41610 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 15 Dec, 2010 1 commit
-
-
Tatuya Kamada authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41456 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 11 Oct, 2010 1 commit
-
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39030 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 14 Sep, 2010 1 commit
-
-
Julien Muchembled authored
getTransactionalVariable has always been implemented to return a global cache object (1 per thread): old implementation used the given context only to have access to the portal. So we enforce this with a warning to make sure people don't expect retrieving 1 cache object per given context. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@38366 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 19 Aug, 2010 1 commit
-
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/sandbox/amount_generator@37909 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 18 Aug, 2010 1 commit
-
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/sandbox/amount_generator@37881 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 13 Aug, 2010 1 commit
-
-
Yoshinori Okuji authored
Revert the previous change partly, because searchRuleList omits invalidated rules, so even if searchRuleList does not return a rule, it can be due to the validation state instead of the result of a test method. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@37781 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 12 Aug, 2010 1 commit
-
-
Yoshinori Okuji authored
Use references only, as using portal types as keys does not make sense. Also, skip calling Rule.test, because it should have been called implicitly by searchRuleList. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@37739 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 10 Aug, 2010 1 commit
-
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/sandbox/amount_generator@37671 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 03 Aug, 2010 2 commits
-
-
Aurel authored
method from ProperyRecordableMixin git-svn-id: https://svn.erp5.org/repos/public/erp5/sandbox/amount_generator@37458 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
Jean-Paul Smets authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/sandbox/amount_generator@37443 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 27 Jul, 2010 2 commits
-
-
Yoshinori Okuji authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@37276 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
Yoshinori Okuji authored
getCorrectedQuantity must not use a mapped quantity, as any mapping must not be enabled in the simulation world. Instead, every caller must specify which is wanted very explicitly. This change also fixes that delivery error and profit quantity were not handled correctly when quantity was inversed. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@37274 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 15 Jul, 2010 1 commit
-
-
Sebastien Robin authored
Conflicts: bt5/erp5_base/bt/revision bt5/erp5_simulation/DocumentTemplateItem/InvoiceSimulationRule.py bt5/erp5_simulation/bt/revision bt5/erp5_trade/SkinTemplateItem/portal_skins/erp5_trade/Base_viewTradeFieldLibrary.xml bt5/erp5_trade/bt/change_log bt5/erp5_trade/bt/revision products/ERP5/Document/BusinessPath.py products/ERP5/Document/SimulationMovement.py products/ERP5/Document/TradeCondition.py products/ERP5/Document/TradeModelLine.py products/ERP5/bootstrap/erp5_mysql_innodb_catalog/bt/revision products/ERP5Type/ERP5Type.py git-svn-id: https://svn.erp5.org/repos/public/erp5/sandbox/amount_generator@37129 20353a03-c40f-0410-a6d1-a30d3c3de9de
-