loading table of contents...

Content Server Manual / Version 2107

Table Of Contents Workflow Role Groups

The CoreMedia Workflow installation comes with the following predefined workflows which cover the publication and translation of resources:

  • simple-publication

  • two-step-publication

  • translation

The workflows define workflow roles. Each role is mapped to a group:




A user of this group may start a workflow and create a change set


A user of this group may approve resources in a change set 


A user of this group may publish resources in a change set


A user of this group may start a translation workflow
administratorenA user of this group has some rights on specific workflows for administrative tasks

Table 3.56. Workflow role groups

A user must be a member of a role group to execute the respective task. The groups are automatically created when a workflow is uploaded and have no user rights. To approve or publish a user must also be a member of another group which has the rights on resources to be approved or published. To approve a content item A in a workflow, for example, the user must be a member of

  • approver-role to be able to accept the approve task in the workflow and

  • a group which has APPROVE rights on the content item A

In an LDAP-enhanced CoreMedia system, Workflow role groups are mapped in the Workflow Server properties.

# remap roles for default workflows

Example 3.50. Groups in Workflow Server properties

These are looked up only once when uploading the workflow. See the Workflow Manual for a more detailed description of Workflow Server properties.

The translation-manager-role must match the setting in the property sitemodel.translationManagerRole of the site model, see Section 5.5, “Localized Content Management” in Blueprint Developer Manual for details.

Search Results

Table Of Contents

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.