1. 12 Aug, 2020 5 commits
    • Jérome Perrin's avatar
      Update Configurator Simulation Configuration · b08338c8
      Jérome Perrin authored
      Configuration generated by Standard Configurator was not really good. For most divergences, there was no solvers configured, so users could not configure divergences. Now solvers (for packing lists) are configured so that every divergence is automatically accepted, we only expect user to take a decision when quantity or resource is different.
      This change was implemented in the rules from `erp5_configurator_trade_template`, but because several simulation tests were relying on the fact that "changing anything would cause a divergence" the previous rules configuration are kept in a new `simulation_test_trade_template`.
      
      Also, security configuration was incomplete, since the introduction of "new simulation", some Unauthorized errors occurred when non-manager users where trying to solve divergence. This is now solved and exercised in the integration tests we run on auto-configurated instance. 
      
      The configuration was obsolete, nowadays we use different business processes for each use case, this configuration was still using only one business process for both sale and purchase, now we use two and improve the accounting configuration, to use accounts defined in supply line.
      
      Some others small improvements were made, for example now we can configure the delivery solver to use for a split solver once and for all in the solver and user does not have to choose each time.
      
      What not updated this time:
       - divergences on Invoice Lines: this is probably same as on Packing List before these changes
       - rules are still configured with ad-hoc scripts and not based on trade phase categories.
      
      See merge request !1221
      b08338c8
    • Jérome Perrin's avatar
      Fix translations with ${portal_type} variables · 349258e5
      Jérome Perrin authored
      See merge request !1236
      349258e5
    • Jérome Perrin's avatar
      BusinessTemplate: update tools, except legacy tools · a52c7d5d
      Jérome Perrin authored
      Since 248f59e5 (Business Template: Likewise ERP5Site.addERP5Tool(), do
      not re-create Tool if it already exists., 2020-06-22) we no longer
      update tools, because of the problem that business template does not
      currently handle updating objects with lots of sub-objects.
      
      But we realized that we really need to update tools when they contain
      configuration as object attributes, like mimetypes_registry, where the
      problem was observed.
      
      Instead of unconditionnally skipping any tool during update, we only
      skip the ones that were initially managed by ERP5Generator and are moved
      to business templates.
      a52c7d5d
    • Jérome Perrin's avatar
      officejs_support_request_ui: use "Submit New Support Request" for form name · 18484163
      Jérome Perrin authored
      to match the button on the front page
      18484163
    • Jérome Perrin's avatar
      ui_test_core: support updating snapshot image behind virtual host · e37dfeb6
      Jérome Perrin authored
      With virtualhosting, there can be an empty path element at the beginning
      of the path.
      e37dfeb6
  2. 11 Aug, 2020 2 commits
  3. 10 Aug, 2020 2 commits
  4. 07 Aug, 2020 10 commits
  5. 06 Aug, 2020 8 commits
  6. 05 Aug, 2020 4 commits
  7. 04 Aug, 2020 4 commits
  8. 03 Aug, 2020 5 commits