But whenever it is set, it shall be correct XML.

By registering noop activity on alarm itself which depends on tag used in alarm
only one alarm will be run in same time.

slap_interaction_workflow has already global scope of interaction, so keep it
like this and do not add yet another workflow to do one interaction.

Some Software and Slave instances can have too old clenaup deliveries.

Any correct XML is accepted, even if as dict it evaluated to false, so if call
to getInstanceXmlAsDict succeed evaluate expression to true.

Whenever it is changed, all related delivery lines have to be reindexed, as
this impacts software_release table.

Provide updated revision files.

Conflicts:
	master/bt5/vifib_base/bt/revision

There is no need to get the root software instance, as the hosting subscription already contains the needed information

This ease usage of slapgrid (if triggered less than each 5 minutes)

There is no need to get the root software instance, as the hosting subscription already contains the needed information

Conflicts:
	master/bt5/vifib_erp5/bt/revision
	master/bt5/vifib_slap/bt/revision

It might happen that something else is newer then cleanup delivery (eg. because
of user was able to ask to stop/start just after cleanup).

So clone currently waiting cleanup delivery with date newer then previous one
and replace it. Thanks to this instance destruction will be possible.