This is required for multiple sites support and allow us write unit tests and not create a 100 lines mock.

   This allow the administrator define which Login portal types are searched.

Also extend tests to cover recently changes

   This is an alternetive way to login using Certificates. Probably this format
   will evolve into use caucase;  however this only introduce some most basic features.

   Use Certificate Login for store login definitions

  Please squash me in future.

  This optimisation aims reduce the potential activity leak when over launching accross multiple activities/transactions the updateSimulation.
  SubscriptionItem: Add a method to call updateSimulation from sqldict activities
    updateExpandableRootSimulation allow launch activities in a safer matter and have lower calls.

  If the user wants actitivites, it should create multiples StandardBT5ConfiguratorItems,
  This should accellerate Tests based on ERP5Configurator.

  This should be recoded, but it should speed up bootstrap of a site,
  as get modified objects are not called.

It the user don't have fully permission on the object (already changed state), this set will fail to check if source should be defined.

Ignore list is usefull when you have old business templates in production (used to include data for example) and test business templates on test environment (ie;: erp5_test_ui_core). This allow us control the dump to assert changes easily.

1 minute is too agressive for general use.

  The upgrade ordering seems buggy and requires to force reinstall it

This allow during a subscription process, create a user and them create all
documents using that user w/o rely on proxy roles (keeping good ownership
across the documents).

Without this (on slapos master ui) the redirection places value unquoted causing parser to fail later on when resolve {n.me}

  The user can be present from diferent logins, password tool only works with ERP5LoginUserMager
  users.

Mixed commit:

  43b1ae1b
  2f05fe1b

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

Note: Generic code shall have no constraints at all.

Conflicts:

	bt5/erp5_accounting/bt/revision

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

See 6c4f7600

Allows to keep UI tests working independently of the login process
implementation details.

This reverts commit e5c160bc.

in API script AccountingTransaction_createReversalTransaction

Opening an accounting period is refused if the start date of the period
is more than one day after the stop date of the previous period, but this
check did not take into account that "next day" might be more than 24
hours, like it's the case when daylight saving happen between these dates.
Instead we check that the difference is less than 1.9 days.

Reorganise tests to group accounting period related tests in a dedicated
test class and add missing tests for period validation checks.

Also fix a few race conditions with catalog indexing that are probably not
a problem in real life but were revealed by the test.

See SQLBase._getExecutableMessageSet for operation principle.
Removes the notion of order_validation_text: activity validation is no
longer evaluated per-activity , but per-dependency for multiple activities
at a time. In this context, order_validation_text does not make sense as
it flattens all dependency types for a given activity.
Rework activity-dependency-to-SQL methods: use a dict rather
dynamically-generated method names.
Based on initial work by Julien Muchembled.