Previously, portal_type parameter was passed in REQUEST and stored in the selection for the next listbox, which can be listing objects of another portal_type

Accounting Transactions are chained with 2 workflows, but delivery_causality_workflow is an exception to module level "change state"

add accounting lines manually, are they are not added by init script anymore when erp5_invoicing is installed

This reverts parts of 3b22ae1f
As the field has default_to_now set, if we save "" it will display now

Also note that we could take a screenshot if test times out.

For now the test reading tables from erp5.com are still disabled.

A TargetSolver might have its configuration updated multiple times, if the same
solver type was chosen for different divergences (solver_decisions).

We must take care not to overwrite configuration from earlier updates with the
data from later ones.

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.

New simulation movements don't have a .divergence_scope attribute, so
movement groups should not assume their presence when checking scope to
adopt a divergence.

Instead of expanding one below it that might not have been modified at all.

cause running out of memory so enforce some restrictions by default which will prevent this.

This updates several alarms after commit 9c94ae13
("Remove default limit on builders' ZSQL select methods").

If there are more simulation movements, the rest is processed next building time.

Proper way is to call a global builder with a 'limit' parameter.

Use of catalog to get related simulation movements from delivery lines/cells is
unreliable.

Until now, for any new code written for simulation, we often had to be careful
not to call getDeliveryRelatedValueList too early, usually by deferring code
to activities with complicated dependencies. Race conditions are difficult to
avoid by developping this way, because for a given delivery, there are
potentially so many events that happen at the same time, involving:
- simulation, amongst causality, expand, building, solving (including split)
- alarms, user actions, external interfaces, chains of activities
- several related deliveries and simulation trees

This commit enables ZODB-indexing of related documents for 'delivery' base
category, making getDeliveryRelatedValueList safe and fixing unlink of
deleted delivery lines/cells.

Existing activity dependencies are left unchanged because builders only uses
catalog and local building needs to find all simulation movements.

This must prevent the useless download of bt5 which are already installed
And so this is supposed to reduced the number of bt5 installed by configurator and make it faster