The example translation workflow is meant to be configured to your needs. You might define multiple translation workflows, like translation via translation agency or manual translation performed by the site managers.

The only restriction is that every translation workflow needs a process variable subject of type String, which will be set by the framework.

In order to reliably track content that is currently "in translation", you also need to define, configure and regularly invoke an instance of the com.coremedia.translate.workflow.impl.CleanInTranslation class. An example definition is included in the blueprint source in the com.coremedia.blueprint.workflow.boot.BlueprintWorkflowServerAutoConfiguration file, which you may have to adapt.

Be aware, that changes in the process definition will probably lead to changes in the UI, too. If you want to change only small bits of the provided translation workflow like adding another user-selectable translationAction and Task, this can be done pretty easily through configuration of the defaultTranslationWorkflowDetailForm inside the ControlRoomStudioPlugin.

But if want to use a workflow completely different to the one provided, be prepared to write your own implementations of the workflowForms and start panel used to display your workflow in Studio.

For details on customizing workflows see the Workflow Manual. For details on customizing the Studio UI for the translation workflows see Section 5.5.3.5.2, “Translation Workflow Studio UI”.