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.