Like this :
- we see immediately what is selected
- no risk to remove by mistake something already selected
- much more convenient to change
The only tiny drawback is that the look might be a bit different when many values are selected.

Because we want to display "Detailed Aged Balance" and not "Detailed aged
Balance"

some script pass group_by=('function_uid',) instead of group_by_function=1, resulting behaviour in the end must be the same

other ZEO clients even if ZODB Components are not.

Steps to reproduce:

  1/ On zope1, view and edit a person to make sure class is fully loaded.
  2/ On zope2 add an interaction in person_interaction_workflow and add a script raising an exception.
  3/ Edit a person on zope2. The exception is raised, confirming that the interaction is called.

  When editing a person on zope1, the exception is not raised.

ZODB Components: Rename common view to ComponentMixin_view (naming conventions and clash with erp5_pdm).

Before, the field value cache was only invalidated on the node where a field
has been modified, so similarly to reset of ZODB Components, implement
synchronization on all nodes through ZODB Cache Cookie.

Instead of hiding those lines and printing an incorrect document it's safer to
let the unauthorized error happen.

Prevent access to locale-dependent and stdout-writing functions.

This is to keep procedure compatibility ( My Favorites / Preferences / Action ... Change Password)

we only had destination_advice_relative_url and source_advice_relative_url acquired properties.

Add following six categories:

 source_decision_administration
 destination_decision_administration

 source_carrier_administration
 destination_carrier_administration

 source_section_administration
 destination_section_administration

Definitions:

- source/destination_decision_administration:
  An entity who receives order and do paperwork for order.

- source/destination_carrier_administration:
  An entity who handles shipment and do paperwork for shipment.

- source/destination_section_administration:
  An entity who do paperwork for invoice.

Simulation relationship fails in (at least) two cases:
- cancelling an invoice which was entirely created by simulation would
  create an empty invoice
- cancelling an invoice with simulated accounting lines generated from
  temp-object-based simulation would copy those lines, while they should
  not be copied
Also, implement recursive copy of Invoice Lines, as (per portal type
definition) they can be arbitrarily nested.
Also, prepare a place-holder for Invoice Cell copy. As I do not have a
document with cells at hand, and do not know all relevant properties, I
decided to keep this code disabled and raise.