Content Locking and Workflow

Content locking can affect transitions between states of a workflow. As the default behavior for the transitions of a workflow, if the content is locked for a publisher when sent to the next state, the content will automatically be unlocked, regardless of the type of lock. However, this behavior is configurable in the workflow XML files (workflowdefinition.xml, if the default lumis workflow is used). For each transition that will not follow the default behavior, the <transition /> element must include the lockAction attribute, whose possible values are:

• unlock: always perform the unlocking during the transition, and
• keepCurrent: will maintain the lock state, if in the next state of the workflow, the user has access to the content; otherwise, the content will be unlocked.

If the lockAction attribute is not specified, the value unlock is used implicitly.