This way it is isolated it in a transaction that is less likely to fail. Activate with max_retry=0 and conflict_retry=False not to send activity twice in case of error.
As with email, if there was an error in activity processing, it is advised to investigate the transport logs to see if message was send or not.

event_simulation_workflow already call `send` type based method upon start transitions.
This workflow was not chained to portal_type, but if it would have been then message would be sent twice.

see !60

When a currency exchange line is (in)validated, we need to reindex the currency exchange
cells that acquire validation state from the currency exchange line.

This allows defining an exchange rate without end date

codemirror python's completion just complete on builtins, so that hack is a bit better

The real motivation was to make sure that search match is displayed when searching with Ctrl+F / Ctrl+G

codemirror: display an animation in window title so that the window flash when component has been saved.

Use case: save component on one tab, go to "run live test" tab and wait for component to be saved to make sure code runs with latest version

Since sending email will not work without destination email, we can globally set this constaint

This sends too many emails.

Some parts were outdated

This reverts commit f0808ac6.

Otherwise test will fail because the user is not indexed yet

test: update causality state explicitly because normal users have no write to modify in solving state.

Because solve() is now unrestecred method.

This reverts commit ab9e6e69.

they are mostly 'Modify portal content' permission.

With ZODB Components, getBusinessTemplateList() only returns the test
bt5 (as given on the command line, such as BT_TITLE:testFoo) and later
it resolves dependencies.

So filtering bt5 to be updated should be done as late as possible...

Selection.__call__() calls getParams() and as getParams() can be called
directly from many places (such as SelectionTool.getSelectionParamsFor()),
it makes more sense to have it here.

1. On Tab1, from PurchaseSupply_view, click on 'Purchase Supply Lines':
   Base_viewListMode??proxy_form_id=PurchaseSupply_view&proxy_field_id=listbox

   This Python Script initialise 'list_mode_proxy_selection' with the
   above 2 GET parameters and then displays PurchaseSupply_view.listbox
   indirectly but current Form is Base_viewListModeRenderer.

2. On Tab2, from SaleSupply_view, click on 'Sale Supply Lines':
   Base_viewListMode?proxy_form_id=SaleSupply_view&proxy_field_id=listbox

   This Python Script initialise 'list_mode_proxy_selection' with the
   above 2 GET parameters and then displays SaleSupply_view.listbox
   indirectly but current Form is Base_viewListModeRenderer.

3. On Tab1, filter Purchase Supply Lines.

   As proxy_form_id and proxy_field_id are not given, then
   Base_viewListModeRender fallbacks on 'list_mode_proxy_selection'
   values to find out the Form ID to be called and wrongly display
   SaleSupply_view.listbox (2.).