1. 16 Mar, 2017 2 commits
  2. 15 Mar, 2017 4 commits
  3. 14 Mar, 2017 2 commits
  4. 13 Mar, 2017 2 commits
  5. 10 Mar, 2017 5 commits
    • Xiaowu Zhang's avatar
      erp5_core: Update jio.js to version 3.14.0 · 89be9bdc
      Xiaowu Zhang authored
      89be9bdc
    • Xiaowu Zhang's avatar
      d2b6c349
    • Yusei Tahara's avatar
      erp5_data_notebook: Don't save ZBigArray in data notebook. It may be too big... · 5fb16acd
      Yusei Tahara authored
      erp5_data_notebook: Don't save ZBigArray in data notebook. It may be too big that zope process may crash.
      5fb16acd
    • Jérome Perrin's avatar
      Merge !236 accounting: fix accounting period constraint with node acquisition on invoices · 5005c662
      Jérome Perrin authored
      from commit message
      > We have a constraint preventing closing accounting periods if there are still some accounting transactions that are in "current states" (ie. not delivered / cancelled), but this constraint should not be fooled by accounting lines in stock table that does not have an account as node, but just an acquired organisation.
      
      We already fixed another problem where such lines where "getting in the way" in c61cde5b
      
      But here, it's at inventory level, we want to get "all accounting movements from this section during the period"., excluding these "not really accounting" lines.
      
      I used the same approach as the one we applied when we discovered in !215 , there was code doing:
      `getInventoryList(node_category="account_type")`
      as a way to get only movements on accounts, relying on the facts that accounts have an account type category.  This stopped working and we accepted it because this use case was not really valid. Instead, we did a first query getting all account and passing this as a `getInventory(node_uid=`
      
      I don't think we want to support `node_portal_type` in Inventory API, because the concept of *portal_types* does not really belong in Inventory API to me.
      
      To  prevent creating many portal types (Tax, Discount etc) we concluded:
       * Resources (and Movements) are classified by their *use* category
       * Deliveries are classified by their *ledger* category
       * Nodes are classified by their *role* category
      
      So the "pure" approach is maybe to add a role category on all accounts and query inventory with `getMovementHistoryList(node_category="role/accounting_node")`.
      
      I'd say let's merge this for now, but if you have better idea or anything to add please go ahead, I wanted to create an open place for discussion and explaining why i did all this.
      
      /cc @tc @vpelletier @georgios.dagkakis @Nicolas
      
      /reviewed-on !236
      5005c662
    • Jérome Perrin's avatar
  6. 09 Mar, 2017 1 commit
  7. 08 Mar, 2017 4 commits
  8. 07 Mar, 2017 5 commits
  9. 03 Mar, 2017 2 commits
  10. 02 Mar, 2017 1 commit
  11. 01 Mar, 2017 2 commits
  12. 24 Feb, 2017 2 commits
  13. 20 Feb, 2017 3 commits
  14. 18 Feb, 2017 3 commits
  15. 17 Feb, 2017 2 commits