Configure the Project Workflow
Info: The Project Workflow feature in Bloomreach Content requires a standard or premium license. Contact Bloomreach for licensing details.
Overview
This page describes how to configure the workflow for the Projects feature in Bloomreach Content.
When to Use
Configure the project workflow to control approval requirements and restrict direct changes to channel configuration. Use these settings to enforce process consistency and governance for project-based content and configuration changes.
Prerequisites
- Bloomreach Content with the Workflow Process Management add-on installed
- Standard or premium license
- Access to the JCR repository
Project Workflow Configuration
The Workflow Process Management add-on enables the Projects feature, which includes a project workflow. The workflow can be configured using the parameters described below.
Approval Policies
Configure approval policies at the following node:
/hippowpm:hippowpm/hippowpm:approvalpolicies/dx-projects
| Property | Type | Default Value | Description |
|---|---|---|---|
hippowpm:requiredAccepts | Long | 2 | Number of approvals required before a request is accepted. |
hippowpm:ignoreDocumentReadPermissions | Boolean | true | If true, displays the document name to users without read permission for the document. |
Example Configuration
hippowpm:requiredAccepts: 2 hippowpm:ignoreDocumentReadPermissions: true
Restrict Direct Changes to Channel Configuration
To prevent users from making direct changes to the core configuration of a channel, set the hst:locked property to true at the following node:
/hst:[projectname]/hst:configurations/[channelname]
| Property | Type | Default Value | Description |
|---|---|---|---|
hst:locked | Boolean | false | When set to true, CMS users cannot make direct changes to the channel core and must use the Projects workflow. |
Important
- Locking the core applies only to channel configuration, not to content.
- Due to a known UI issue, the menu editor remains accessible in a locked core channel, but changes made there cannot be saved.
Example Configuration
hst:locked: true
Verification
- To verify approval policy changes, initiate a project and confirm that the required number of approvals matches your configuration.
- To verify channel locking, attempt to edit the channel configuration directly. The UI should prevent changes unless they are made through the Projects workflow.