Reuse Transaction and Committable for actions and workflows

Action customizer flags 'Reuse Transaction' and 'Committable' are functionally related to some properties of 'start' workflow nodes (e.g. 'Start from EditorView').

Workflow starting from the GUI use special 'start' nodes (e.g. 'Start from EditorView'). These nodes provide properties possibly limiting in which context the workflow (action) can be mapped to GUI.

For example, if the workflow designer creates a workflow intended strictly for use within its own database transaction, he or she will set the workflow start node property 'Independent start=True'. Consequently, when an action using this workflow is mapped to GUI, the 'Reuse Transaction' check box in the 'Assign Actions to GUI' tab for this action will be disabled and non-editable. This way the action cannot be mapped to GUI in an unwanted context.

Workflow start node properties 'Independent start' / 'Inside given transaction' influence the 'Reuse Transaction' property of action mapping in the following way:

Independent start = True Inside given transaction = False	Reuse Transaction = False and cannot be set to True

Independent start = False Inside given transaction = True	Reuse Transaction = True and cannot be set to False

Independent start = True Inside given transaction = True	Reuse Transaction can be set either to True or to False

Independent start = False Inside given transaction = False	This combination cannot be set for the start node properties

Workflow start node properties 'Can commit' / 'Must not commit' influence the 'Committable' property of action mapping in the following way:

Can commit = True Must not commit = False	Committable = True and cannot be set to False

Can commit = False Must not commit = True	Committable = False and cannot be set to True

Can commit = True Must not commit = True	Committable can be set either to True or to False

Can commit = False Must not commit = False	This combination cannot be set for the start node properties