Bloomreach Embargo Plugin

7.0.2

Released: 15 Jan 2024

• FORGE-510
  Improve the embargo set by adding support for multi select for non admin users that belong to more than one embargo groups.
• FORGE-452
  Improve existing security domains for live and preview documents by excluding also the embargo:handle

7.0.0

Released: 6 May 2022

• HIPFORGE-421
  Upgrade to Bloomreach Experience Manager 15: build with Java 11, use Wicket 9, redo the demo.

6.0.0

Released: 15 October 2020

• HIPFORGE-378
  Upgrade to Bloomreach Experience Manager 14.
• Embargo user indication (left menu red background) has been removed.
• Module configuration node is now at /hippo:configuration/hippo:modules/embargo-workflow-module (the node used to be named embargo-workflow-events-processing-module.xml).

5.1.0

Released: 20 January 2020

• EmbargoWorkflowEventsProcessingModule#getUser was broken in 5.0.0, breaking the functionality regarding automatically putting embargo on documents.
• HIPFORGE-331
  Prevent false activity stream items and loggings about setting embargo.
• Slight changes in the mark-up of the activity items, placing words 'handle' and 'document' outside the bold area.

5.0.0

Released: 4 November 2019

• HIPFORGE-326
  Upgrade to Bloomreach Experience Manager 13.
• Restructure the Maven modules; change the artifacts’ groupId to 'org.bloomreach.forge.embargo' (so renaming hippo to bloomreach) and simplify the artifactIds. This requires to revisit the installation page when upgrading.

4.1.0

Released: 20 January 2020

• HIPFORGE-331
  Prevent false activity stream items and loggings about setting embargo.

4.0.0

Released: 19 October 2018

• HIPFORGE-193
  Upgrade to Hippo 12.
• UI improvements in the document set/remove Embargo dialogs.
• Fix a bug where the lock icon didn't show in the "Embargo | Set" menu item for embargo-editors and embargo-authors.

3.1.0

Released: 13 Sep 2018

• HIPFORGE-185
  Remove five non-functional configurations at /hippo:configuration/hippo:workflows/events-embargo-** plus the related Java classes (technical debt).
• HIPFORGE-186
  In the module listening for events as 'embargo user', add the embargo:document mixin at later stage to the document variants, avoiding errors related to disappearing mixins (probably race condition).
• HIPFORGE-189
  Mark the EmbargoWorkflowEventsProcessingModule at /hippo:configuration/hippo:modules/embargo-workflow-events-processing-module.xml as 'cmsonly' to prevent errors on site-only nodes.

3.0.2

Released: 22 Januari 2018

• HIPFORGE-110
  Remove embargo trigger node from (deleted) documents in attic.
• HIPFORGE-132
  While getting the document variants from a handle, do not check for mix:referenceble because it can be missing from draft variant, causing embargo mixins to be present on draft only.

3.0.1

Released: 17 Januari 2017

• HIPPLUG-1421
  Use the Hippo 11 style translations for the Embargo workflow name.
  Note: when deploying this version, make sure the repository bootstraps by setting -Drepo.bootstrap=true.

3.0.0

Released: 28 November 2016

• Upgraded for Hippo 11.

2.1.8

Released: 24 July 2018

• HIPFORGE-186
  In the module listening for events as 'embargo user', add the embargo:document mixin at later stage to the document variants, avoiding errors related to disappearing mixins (probably race condition).

2.1.7

Released: 6 June 2018

• HIPFORGE-168
  Back porting both HIPFORGE-110 and HIPFORGE-132 from the Hippo 11 version to the Hippo 10.2 version.
  - Remove embargo trigger node from (deleted) documents in attic.
  - While getting the document variants from a handle, do not check for mix:referenceble because it can be missing from draft variant, causing embargo mixins to be present on draft only.

2.1.6

Released: 2 June 2016

• HIPPLUG-1294
  Changed columns width (columns were too wide).

2.1.5

Released: 6 April 2016

• HIPPLUG-1281 follow-up
  Add wait time before adding embargo workflow, by default 500 millis, configurable by Long property 'waitTime' at /hippo:configuration/hippo:modules/embargo-workflow-events-processing-module.xml.

2.1.4

Released: 1 April 2016

• HIPPLUG-1281
  Added listener to put newly created documents under embargo.
• HIPPLUG-1282
  Images and assets are now under embargo when created by an embargo user.
• HIPPLUG-1283
  CSS fix for list view of documents.
• HIPPLUG-1284
  Embargo documents excluded from number of search results.
• HIPPLUG-1285 Show embargo end date in the CMS.
• Added version to cnd reload so the cnd is actually reloaded.

2.1.0

Released: 1 March 2016

• Upgrade to be compatible with Hippo 10.1.

1.03.00

Released: 10 February 2016

• Upgrade to be compatible with Hippo 7.9.

1.02.00

Released: 2 February 2014

• Admin user can now set documents under embargo. A dialog is shown so he can select which groups to use.
• Upgrade to be compatible with Hippo 7.8.

1.01.06

Released: 16 August 2013

• Resolved issue with content items losing the embargo status when being copied.
• The embargo workflow is from now on only shown if a user has the hippo:author privileges for a document.
• It was not possible to change the date/time of the scheduled embargo removal even if the date/time was still in the future.
• Increased code coverage.

For systems that used version 1.01.05 there is an updater module available which will update the plugin configuration to the latest version.

1.01.05

• Embargo workflow event may be fired from a non-cms context, so we don't call the embargo feature from a remote (RMI) application.
• Increased code coverage

1.01.02

• New content created by an embargo enabled user, is automatically put under embargo.
• Rescheduling/ cancelling embargo schedule.
• Embargo content does not appear anywhere for non embargo users/ or in site.
• i18n for properties.
• Documentation/ licensing.

1.01.01

• Initial commit.
• Set/remove embargo features.
• Embargo domain declaration.
• Workflow in place.
• Admin can create more embargo groups/ users.
• Embargo for images and assets additionally to documents.