It is required to match movements.

It allows to match not directly connected Simulation Movements with links.

It is implicitly set by Business Process, and as it is dynamic in lazy case do
implicit update comparison.

Context can be None, there is no need to log.

getBusinessLinkValueList method is called many times without context and this
pollutes log heavily.

add empty init scripts for Person and Organisation so that we can override init script without overriding these portal type definitions themselves.

Accept business_link_list on searchMovementList in order to test each found
movement precisely against Business Process.

If any Simulation Movement will become not buildable anymore reset causality
link.

When calling searchMovementList pass Business Links in order to allow select
only interesting movements.

Use predicate test method of Business Links in order to find matching one.

Fail in case if none found or in case if predicate matches too many.

Note: As updated design assume that Simulation Movements w/o Business Link are
not buildable at all it will render all "legacy simulation movemements", those
pre-Business Process, to be non buildable.

During expand check if movement is buildable and only then allow to set
causality link to Business Process.

http://www.imagemagick.org/Usage/masking/#remove

If no module is selected, check nothing.

There is no control where context would be used.

remove Delivery_viewSolveDivergenceDialog in erp5_base because it already exists in erp5_simulation or erp5_simulation_legacy.

add a hidden field in Delivery_viewSolveDivergenceDialog so that user are forced to update the dialog first.

fix a condition of Person_view/my_default_email_url_string so that only one email field is displayed on a new Person document.