Create only one and use tag in order to avoid race conditions.

There are just two states, and unlocked one allows to request Software Instance.

It checks all Persons and depending on thier balance and due date locks/unlocks.

Person is locked when thier balance is lower then configured one or when there
is ongoing payment older then accepted due period.

Person is unlocked when thier balance is higher then configured one and when
all ongoing payments are in acceptable time period.

It is required to visit every workflow object and click save after
manipulation of states.

Just two alarms which are checking is Software/Slave Instance shall be locked.

open_order_url is used rarely.

Use only one state -- locked.

But use transition, which are able to store open_order_url, if found.

Expose lock and unlock transition, which will selectively use correct helper
transitions with or without storing open_order_url.

This reverts commit ee2553c6.

Conflicts:

	master/bt5/vifib_slap/bt/revision

This reverts commit 296fdfb7.

Conflicts:

	master/bt5/vifib_base/bt/revision
	master/bt5/vifib_slap/bt/revision

Person and Software Instance state has changed from slap_state to payment_state.

Person and Software Instance slap states have to be catalogged so reuse
existing column.

This is future compatible, as same state will be used to lock operations
of Person or Software Instance.

Create only for two months in advance.

Warning: if you thought that Romain's hack was dirty, this
is worse. Anyway, this could suffer from having several
slave instance with the same title. Be aware.

Conflicts:

	master/bt5/vifib_slap/bt/revision

Do not scatter so much between Business Templates portal type definitions.

Warning: if you thought that Romain's hack was dirty, this
is worse. Anyway, this could suffer from having several
slave instance with the same title. Be aware.

Conflicts:

	master/bt5/vifib_slap/bt/revision

Do not scatter so much between Business Templates portal type definitions.

Warning: if you thought that Romain's hack was dirty, this
is worse. Anyway, this could suffer from having several
slave instance with the same title. Be aware.

vifib_open_trade is required before vifib_slap.

variation property which comes from Item generates getVariationPropertyList.
VariationRange's property defines variation_property which also generates
getVariationPropertyList

As there is conflict which is not solved by category accessor generation
sorting (which is per property sheet) adding later VariationRange will result
in overwriting accessor for category with own one.

Periodicity like original one (on Sunday).

Configured to check all objects (no module restriction, no additional query)
and to send notification in case of problem.