The CoreMedia Workflow installation comes with the following predefined workflows which cover the publication of resources:
simple-publication
two-step-publication
The workflows define workflow roles. Each role is mapped to a group:
|
Group |
Description |
|---|---|
|
composer-role |
A user of this group may start a workflow and create a change set |
|
approver-role |
A user of this group may approve resources in a change set |
|
publisher-role |
A user of this group may publish resources in a change set |
Table 3.49. 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
workflowserver.properties file.
# remap roles for default workflows #roles.map.approver-role=approver@example.org #roles.map.composer-role=composer@exmaple.org #roles.map.publisher-role=publisher@example.org
Example 3.33. Groups in workflowserver.properties
These are looked up only once when uploading the workflow.
See the [Workflow Manual] for a more detailed description of workflowserver.properties.
 |  |  |
 |