Avoid getting the list twice, follow coding style, explicitly access portal
methods on portal.

Remove condition to test if the event path destination predicate applies for this destination. On this this case, we can trust on the previous selection using the domain

call getObject() once explicitly to reduce number of calls.

this code was working just by chance because active_knowledge_pad is a brain, not an ERP5 object.

Revert "fix undefined variables"

This reverts commit 77a53809.

Revert "Listbox: calculate a mapping uid -> object once"

This reverts commit 84029c01.

Revert "fix list method returning duplicate uids"

This reverts commit 386b0e6b.

Revert "test for dialog listbox with editable fields"

This reverts commit e046d8f5.

Instead of looping through the list each time.
Also check that the list method does not return duplicate uids.

This cache is used by AccountingTransactionLine_getNodeItemList

It is useless to clear the cache in activities, because this would only work when using only one zope instance. Instead, clear the cache in the test for now.

Also do not hardcode 'business_process_module'.

>>> self.closure_cache[business_link] = new_business_process
was done after 'business_link' was overridden by the for loop.

This also the following line in getBusinessLinkClosure():
  if simulation_path.startswith(path):

For example, '/erp5/portal_simulation/1/10'
should not match '/erp5/portal_simulation/1/1'

amendments to dd69a61c, unsubcribe / subscribe instead of changing alarm node

mistakenly removed in a8b2267c

With this change, code like the following will use much less memory.

  for i in portal_catalog(...):
    i.activate().method()
Signed-off-by: Vincent Pelletier <vincent@nexedi.com>

so that we can register activity by path from restricted environment.
also set default parameters just same as ActiveObject.activate().

so that we can call ActivityTool.activateObject() with not only by
object but also by it's path.
Signed-off-by: Vincent Pelletier <vincent@nexedi.com>

Fix open order simulation interactions, when using "trigger once by transaction", it's better to call the script at end of transaction

Some callable are instances with __call__ methods and
ZPublisher already expects them to provide useful func_code & func_defaults.

This is a quick workaround, the main problem is that get_request is monkey
patched to use a completly different implementation in tests, and in some cases
this monkey patch is not properly applied.

Because edit adds a line in workflow_history