It will protect against storing truncated data.

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

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)

Also minimise activity hurricane by calling expand directly.

Open Orders are searched using indexation timestamp, which allows to see them
in "windows", and does not repeat expand if not needed.

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.

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.

Notes:

Do nothing on 'calculate' instead of disabling *_causality_interaction_workflow as
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.

This commit also update list of method_id which should not call calculate_causality

Conflicts:
	bt5/erp5_crm/bt/revision

 - Acquire subordination from parent Computer: Thanks to this Computer Partitions
     can be in same category as Computers they are contained in.

 - Computer should acquire region from parent.
 - Add group acquisition on Computer Partition

getOwner returns a python document.

Only support Base_jumpToRelatedObject for now.

fix the keys adding 'portal_type_workflow_chain/'
in _importFile, preinstall and export."

This reverts commit 6f8221b6.

This commit cleaned inconsistent prefix manipulation in
PortalTypeWorkflowChainTemplateItem. It passes the test suite,
however it was found to produce incompatibility with previously installed
business templates. In 'Upgrade Business Templates from Repositories"
there was a diff of PortalTypeWorkflowChainTemplateItems like:
Portal Type Name -> New
portal_type_workflow_chain/Portal Type Name -> Removed
For some reason the upgrade process would remove the chain
without adding the new element.

We are working on a clean solution, but since this needs more testing
I revert this commit for now so that master version does not cause
problems to users.

parameters "develop = false" and "revision =" are now set every time

fix the keys adding 'portal_type_workflow_chain/'
in _importFile, preinstall and export.

ReportSections are rendered as 'embedded' forms.

As selections are not used in erp5js, any python code (TALES expresssion for example) accessing them will not return the expected value. Such code should probably be rewritten (no idea how yet).

Add Semaphore functionality on adding Log to history.

Implementation of Delivery Receipt sending. Delivery Receipt hadnling is
not implemented yet.
http://xmpp.org/extensions/xep-0184.html

clients which support xep-0184
adnroid: https://conversations.im/ https://www.xabber.com/
linux: http://psi-plus.com/

/reviewed-on nexedi/erp5!76

business templates were brought to previous format,
removing 'portal_type_workflow_chain/' prefix

remove 'portal_type_workflow_chain/' from the keys in export.
This is added in _importFile and in build the key becomes the portal type
So if the business_template was exported without being built there was a diff.

Portal Type as Classes: Fix memory leak: Workflow method list was never emptied and thus reset Workflow Methods were never GC.

Implementation of Delivery Receipt sending. Delivery Receipt hadnling is
not implemented yet.
http://xmpp.org/extensions/xep-0184.html

clients which support xep-0184
adnroid: https://conversations.im/ https://www.xabber.com/
linux: http://psi-plus.com/

it save from message loss.

This change allows easily track if some test suite has enough test nodes
 to run or not.


/reviewed-on nexedi/erp5!78

After that change, when there is a movement from A to B in **started** state, `Item_getCurrentSiteValue` will consider that this movement has already reached B.

Before this change, `Item_getCurrentSiteValue` was returning None, which somehow makes sense because started movement is in transit state, so the item has left A but not yet reached B, so it is in an unknown location.
Low level current tracking list API ( getCurrentTrackingList ) does not return items for started movements.
Honestly, I do not know if this is by design. (  anybody knows ? )

I will work on adding missing tests, but please tell me if I am wrong in thinking it should return None.

@gabriel @rafael @tb @tc do you remember why this change was introduced ? Maybe that behaviour of returning None should be only at the level of `Item_get*` scripts ? 

/reviewed-on nexedi/erp5!70