Return to doc.sitecore.com

Documentation

This module allows developers to move language versions of an Item to a certain workflow state depending on the workflow state of another language version.

Such functionality allows modifying the default behavior when all language versions have separate workflows.

1.  Installation Guide

The Set State by Language module is distributed as a standard Sitecore package. Thus to start using it, you should install the package. Please refer to the Installing Modules and Packages article if you are not familiar with the standard Sitecore Packager tool.

The package installs SetStateByLanguage.dll and ExecuteCommand.dll assemblies to the “/bin” folder of your site, adds the SetStateByLanguage template and the SetStateByLanguage master to the Client.

2.  User Manual

To implement the module’s functionality, you need to do the following:

Below is the detailed description of the steps mentioned above.

2.1.  Creating an Action Item

Choose the workflow state and workflow command which you want to trigger the change of the workflow state of other language versions.

Create a new action for the command using the SetStateByLanguage master.

 /upload/sdn5/shared library/workflow/set state by language/setstatebylanguage1.png

Edit the action:

Use the AllowedToChangeStates field to select the workflow states which will be taken into consideration when the action is executed. For example, if only the Editing state is selected, the action defined in the CommandToExecute field will only be applied to the language versions of Items in the Editing state.

/upload/sdn5/shared library/workflow/set state by language/setlanguagebyselection2.png

Use the CommandToExecute field to define a command which you want to be applied to the language versions.

/upload/sdn5/shared library/workflow/set state by language/setstatebylanguage3.png

If a User enters a value different from a valid command in this field, usual workflow rules will be applied.

Note : Certain combinations of the AllowedToChangeStates and CommandToExecute values may cause infinite workflow loop.