An error occurred fetching the project authors.
  1. 06 Apr, 2020 1 commit
    • Rafael Monnerat's avatar
      Make Builder able to generate Temp Objects · 9f9fe776
      Rafael Monnerat authored
       Introduce temp_object parameter on builder.build() and propagate it
       over until the newContent() calls. This change allow use create
       Temporary Documents intestead real ones, like a "preview".
      
      (cherry picked from commit 959776ce50c2e7ee2b8f9945ec91a2e0fbe08619)
      
      Conflicts:
      	product/ERP5/Document/SimulatedDeliveryBuilder.py
      9f9fe776
  2. 14 Jan, 2020 1 commit
  3. 25 Dec, 2019 2 commits
  4. 19 Dec, 2019 2 commits
  5. 27 Jun, 2019 1 commit
  6. 26 Jun, 2019 1 commit
  7. 19 Apr, 2019 1 commit
  8. 21 Sep, 2018 1 commit
  9. 22 Feb, 2018 1 commit
  10. 03 Jan, 2018 1 commit
    • Sebastien Robin's avatar
      stock optimisation: fixed error when stock optimisation was used with inventories · 3a597c96
      Sebastien Robin authored
      generateMovementListForStockOptimisation was raising error when there was inventories.
      The method was assuming that doing getObject() on an inventory line (from
      getFutureInventoryList) was always returning a movement. But sometimes we get
      the inventory itself. So do not use getVariationCategoryList, but use the variation_text
      stored in the stock table.
      3a597c96
  11. 10 Aug, 2016 1 commit
  12. 12 Jan, 2016 2 commits
  13. 02 Oct, 2015 1 commit
    • Sebastien Robin's avatar
      simulation: remove concept of mirror movement (continue) · e8524a08
      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
      e8524a08
  14. 22 Sep, 2015 1 commit
  15. 01 Jul, 2015 1 commit
  16. 30 Jun, 2015 1 commit
    • Sebastien Robin's avatar
      simulation: review generated delivery builder (update existing deliveries, date precision) · 15f08b29
      Sebastien Robin authored
      Up to know, order builders were mostly used having in mind the idea of
      deleting all previously created automated orders.
      
      This way was mostly requesting to run generated delivery builder only
      once per night, assuming there is no users working at that time.
      
      So to allows running very often (many times a day) generated delivery
      builders, allow them to update existing deliveries. This way :
      - automated deliveries could be much more up to date
      - there is no need to delete everything
      - this generate few activities, there is no need of a long calculation
        to update everything
      
      Also, the stock optimization was using dates with a precision of one
      full day. Generic code must support much better precision.
      15f08b29
  17. 10 Mar, 2015 1 commit
  18. 05 Mar, 2015 1 commit
  19. 17 Feb, 2015 2 commits
  20. 16 Oct, 2014 1 commit
  21. 08 Aug, 2014 1 commit
  22. 21 Feb, 2013 1 commit
  23. 29 Jan, 2013 1 commit
    • Leonardo Rochael Almeida's avatar
      When building, edit changes in the right order · e1a07bc5
      Leonardo Rochael Almeida authored
      The builder was taking a carefully ordered list of movement group nodes and
      their suggested changes, and squashing the changes all together in a single
      dictionary for .edit(**kw).
      
      Now we calculate the edit_order to take the movement_group order into account.
      e1a07bc5
  24. 19 Oct, 2012 1 commit
  25. 14 May, 2012 1 commit
  26. 11 May, 2012 1 commit
    • Julien Muchembled's avatar
      Cleanup API of TransactionalVariable and read-only cache · d70587e3
      Julien Muchembled authored
      - New readOnlyTransactionCache context manager replacing
        enableReadOnlyTransactionCache and disableReadOnlyTransactionCache
      - Drop compatibility code that tolerate a dummy context to be passed to
        getReadOnlyTransactionCache and getTransactionalVariable.
      d70587e3
  27. 23 Apr, 2012 2 commits
  28. 21 Apr, 2011 1 commit
  29. 14 Mar, 2011 1 commit
  30. 18 Aug, 2010 1 commit
  31. 05 Aug, 2010 3 commits
  32. 04 Aug, 2010 2 commits