Most of UNG code is part of a UNGDoc skin created during bt5 install in order to not mess with rest of ERP5 UI code.
Adjust test (dirty) accordingly.

you can use portal_alarms/upgrader_migrate_event_workflow_history for migration.

Most of UNG code is part of a UNGDoc skin created during bt5 install in order to not mess with rest of ERP5 UI code.
Adjust test (dirty) accordingly.

- Stop calling rule.test() again.
- For Applied Rule objects that don't specialise to an applicable rule:
  - do not expand built ones;
  - and delete others (e.g. if a new rule matches, replace it).

In the case of Base.asContext, initializing workflow was totally useless
because 'workflow_history' was overridden by the original one.

When sorting on int_index for example, the returned movement list
was in reversed order of the expected one.

This fixes a regression introduced in 77d94dd5
("Speed up RuleTool.searchRuleList by quickly filtering out rules"),
causing TestRule.test_09_expandTwoRules to fail.

UNG code contains overrides of default ERP5 UI and KM UI which breaks it so add theme to its default skin selection (same way as KM).