Usually subscription item portal type does not have a proper tracking, so you may want to use this alarm only on some item portal types

In some configurations this might be incorrect, but for most cases it is not a
good idea that a price that is currently beeing edited gets applied.

At least this is the behaviour expected in my understand

This is required for ERP5Site_checkDataWithScript script (erp5_core BT).

This is not a new feature, this behavior is compatible with the old caching
implementation that was using inventory_stock table.
In other words, this brings backs the backward compatibility in inventory
caching.

(This commit fixes the incomplete tests that was reverted just before.)

Needs more tests.

This reverts commit 74db4d39.

This is not a new feature, this behavior is compatible with the old caching
implementation that was using inventory_stock table.
In other words, this brings backs the backword compatibility in invetory
caching.

omit_balanced_accounts was always displaying 1
omit_empty_accounts should not exist

To display the list of possible accounts we include validated nodes and  nodes that have been previously used on accounting movements. We include 2, because we want the user to be able to issue a report on a node that has been used in the past and is now invalidated.

The problem with this approach is that such query is very slow, when there are a lot of Movements.

Then, with the commit only validated accounts will be considered

This commit is part of 0ee6eae7.

The script ERP5Site_getWorkflowStateItemList that receives the portal type and the state variable (simulation_state/validation_state) as parameters and it will returns the states for the workflow chained to the portal type