1. 06 Jun, 2016 1 commit
    • Julien Muchembled's avatar
      BT: dummy copy to preserve history · 428310a2
      Julien Muchembled authored
      We should have done before committing 76ecef89
      but doing it now with a dummy merge also works.
      
      Unfortunately, this is not really useful for blame, because all lines are
      rewritten, at least to remove the trailing '\n'.
      
      Files that have already been modified in 'master' branch are excluded.
      428310a2
  2. 07 Mar, 2016 1 commit
  3. 04 Feb, 2016 1 commit
  4. 11 Sep, 2014 1 commit
  5. 27 Jun, 2013 1 commit
  6. 28 Jan, 2013 1 commit
  7. 03 Oct, 2012 1 commit
    • Julien Muchembled's avatar
      Simulation: splitted expand, performance improvements and bugfixes · 5c09e2e2
      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.
      5c09e2e2
  8. 25 Sep, 2012 1 commit
  9. 23 Apr, 2012 1 commit
  10. 09 Apr, 2012 1 commit
  11. 29 Mar, 2012 1 commit
    • Rafael Monnerat's avatar
      Move solvers, rules and code from erp5_simulation_test to erp5_configurator_standard_*_template · 399caf39
      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.
      399caf39
  12. 24 Jan, 2012 2 commits
  13. 19 Jan, 2012 1 commit
  14. 05 Jan, 2012 2 commits
  15. 15 Dec, 2011 1 commit
  16. 25 Nov, 2011 1 commit
  17. 21 Jun, 2011 3 commits
  18. 17 Jun, 2011 1 commit
  19. 16 Jun, 2011 1 commit
  20. 09 Jun, 2011 1 commit
  21. 08 Jun, 2011 3 commits
  22. 07 Jun, 2011 1 commit
    • Sebastien Robin's avatar
      on movement collections, use list of properties defined in rules · c64d4287
      Sebastien Robin authored
      Until now, we had in movement collections all possible properties
      found by _propertyMap for every movement. Now movement collections
      use list of properties defined in rules.
      
      This change was breaking some tests because not enough properties
      were expanded, so in the same time it is required to add more
      properties to progagate on several rules
      c64d4287
  23. 24 May, 2011 1 commit
  24. 13 Apr, 2011 1 commit
  25. 17 Dec, 2010 1 commit
  26. 15 Dec, 2010 1 commit
  27. 26 Oct, 2010 1 commit
  28. 13 Oct, 2010 3 commits
  29. 17 Sep, 2010 2 commits
  30. 01 Sep, 2010 1 commit
  31. 31 Aug, 2010 1 commit