some projects uses such states in custom workflows

It is extra information that we had to have more context and be able to
translate differently the same english term in the context of different
workflow.

should always return a list

Also, it will follow the parameters set to the method getProperty

Before chuncks were 1MB big, so with a default zope cache size of 5000 objects,
it was possible to consume 5GB even though the BigFile was filled little by
little with many different transactions.

Sometimes, after saving a Component, Interaction Workflows Methods were not
created, thus reset could not be done later on.

Allows giving more compact and user-meaningful names if desired.
If used, makes in-ZODB data (processing/validation roles) independent
from process' network binding, removing the need to re-configure
CMFActivity after changing network.
Also, update AlarmTool usage of getCurrentNode (and related).
Also, replace AlarmTool's manageAlarmNode input field with a select for
convenience.

Activating constraints is the job of configurator.
I left account_type constraint though, because without this Balance Transaction
creation may not work as expected.

erp5_accounting: Improve Delivery_localBuild to call invoice_builder_alarm only if exist, because in some projects this alarm does not exist

erp5_core: Add External method to access getSecurityCategoryFromAssignmentParentFunctionParentGroup from extensions.erp5.StandardSecurity

Without this script is not possible access the method to generate security policy which will be able to combine parent (for group and function) plus strict base category

Added a security policy which is able to combine parent (for group and function) plus strict base category. It can be useful to generate groups as function* + group* + site, for example.

Predicate security is checked at higher levels