Configure the Project Workflow
This Bloomreach Experience Manager feature requires a standard or premium license. Please contact Bloomreach for more information.
Introduction
Goal
Configure the workflow for the the Projects feature.
Background
The Workflow Process Management add-on adds the Projects feature to Bloomreach Experience Manager which includes a project workflow. At this point, there are only two configuration parameters for the project workflow.
Configure Approval Policies
Node: /hippowpm:hippowpm/hippowpm:approvalpolicies/dx-projects
| Property | Type | Default Value | Description |
|---|---|---|---|
| hippowpm:approvalpolicy | Long | 2 | The number of approvals required before a request is accepted. |
|
hippowpm:ignoreDocumentReadPermissions |
Boolean | true | Show the document name to users that do not have permission to read the document |
| Property | Type | Default Value | Description |
|---|---|---|---|
| hippowpm:approvalpolicy | Long | 2 | The number of approvals required before a request is accepted. |
|
hippowpm:ignoreDocumentReadPermissions |
Boolean | true | Show the document name to users that do not have permission to read the document |
Prevent Changes in Core
Node: /hst:[projectname]/hst:configurations/[channelname]
| Property | Type | Default Value | Description |
|---|---|---|---|
| hst:locked | Boolean | false | Setting hst:locked to true on a channel prevents CMS users from being able to make changes directly to the core of that channel and forces them to use the Projects workflow. |
| Property | Type | Default Value | Description |
|---|---|---|---|
| hst:locked | Boolean | false | Setting hst:locked to true on a channel prevents CMS users from being able to make changes directly to the core of that channel and forces them to use the Projects workflow. |
Due to a UI bug, the menu editor in a locked core channel is still accessible. However, changes made in the menu editor cannot be saved in a locked core.
Locking core only applies to channel configuration, not to content.