PayZen interface expectes all dates in UTC, but suds library is not configurable.
So force UTC usage while importing and using suds, so no date mangling will happen.

Conflicts:
	bt5/erp5_payzen_secure_payment/bt/revision

Mixed commit:

  43b1ae1b
  2f05fe1b

Conflicts:

	product/ERP5/Document/BusinessTemplate.py

Returning true allows to add movements to existing one, and this group shall
always separate them.

uid is used internally during recursive calls and using uid can lead to
traverse all lines of catalog.

Show sorted list, as sorting does not impact sets equality, and, if possible,
format a list in human readable way.

(cherry picked from commit ee7cb2097c4da4bf9a0a7afca1ff2726aa92b2ef)

Acknowledgement can not be displayed without more informations.

Order Builder has same functionality as Devliery Builder.

Note: Generic code shall have no constraints at all.

Conflicts:

	bt5/erp5_accounting/bt/revision

It will protect against storing truncated data.

Changing next_date in certain case cause simulation to create compensation. As compensation is disallowed in commit a2f258eea0a8e58929b61e2ca2ee753c623cf510, changing nexte_date in this cause undesired behavior because of wrong date.

If 2 lines have the same effective date (catalog has a 1 second precision),
always return the validate and open first.

Commit: 02d06501

Changes applied from history:

http://git.erp5.org/gitweb/erp5.git/history/refs/heads/interaction-drop:/product/ERP5/Document/SubscriptionItem.py?js=1

Conflicts:
	bt5/erp5_open_trade/bt/revision

This is a combination of 2 commits.

Fix: post merge with cherry-picked commits on calculate_causality interaction

Don't call calculate_causality after method _setCategoryList

Original commit from : Lukasz Nowak <luke@nexedi.com>
                       3e45ec35

From Lukasz Nowak:

1- Compensation is undesired. (51c8a250)

  Raise loudly with message.

2- Disallow any compensation. (3c74ed07)

3- Emit more informative log. (534b2e77)

Do not *reset* them, as it is normal to have more then one Open Sale Order
with same reference, as other coordinates (like validation_state) are used
to distinguish the documents.

Conflicts:
	bt5/erp5_open_trade/bt/revision

This reverts commit ec8aa158 partially in order
to reenable:
- delivery_causality_interaction_workflow
- delivery_movement_causality_interaction_workflow
- simulation_movement_causality_interaction_workflow

These interaction workflows do not generate activities directly, and do work
that can't be postponed.

By contrast, 'calculate' transition of delivery_causality_workflow is modified
so that no 'updateCausalityState' activity is created by default.

Conflicts:
	bt5/erp5_base/WorkflowTemplateItem/portal_workflow/simulation_movement_causality_interaction_workflow/interactions/calculate_causality.xml

- container_interaction_workflow
- delivery_causality_interaction_workflow
- delivery_movement_causality_interaction_workflow
- delivery_movement_simulation_interaction_workflow
- delivery_simulation_interaction_workflow
- simulation_movement_causality_interaction_workflow
- trade_model_line_interaction_workflow
- transformation_interaction_workflow

Conflicts:
	bt5/erp5_mrp/bt/template_portal_type_workflow_chain_list

Avoid calling isDivergent which can take few minutes to finish.

causality_state comes from well designed causality workflow, which informs
enough about delivery state. Fetching causality_state property is extremely
fast.

Conflicts:
	bt5/erp5_accounting/bt/revision

Conflicts:
	bt5/erp5_open_trade/bt/revision

This is a combination of 4 commits.
Reduce alarm periodicity

Conflicts:
	bt5/erp5_open_trade/bt/revision

Update only few times during the night.

Conflicts:
	bt5/erp5_open_trade/bt/revision

Drop not needed per minute periodicity.

Conflicts:
	bt5/erp5_open_trade/bt/revision

Run alarm really often.

Conflicts:
	bt5/erp5_open_trade/bt/revision

Support full parameter correctly.

Conflicts:
	bt5/erp5_open_trade/bt/revision

Really fix full support.

Conflicts:
	bt5/erp5_open_trade/bt/revision

Drop priority ordering.

Let the activity system chose randomly what to do.

Conflicts:
	bt5/erp5_open_trade/bt/revision

Generate activities and allow to pass the tag. Use search and activate
everywhere which will allow to walk through objects without killing the cluster
even in case of really big documents.

Conflicts:
	bt5/erp5_open_trade/SkinTemplateItem/portal_skins/erp5_open_trade/OpenOrder_updateSimulation.xml
	bt5/erp5_open_trade/bt/revision