[MNT-18543] Method share-header.get.js for Site Presets no longer works with Records Management 2.5.2 Created: 01-Sep-17  Updated: 01-Oct-19  Resolved: 22-Feb-18

Status: Closed
Project: Service Packs and Hot Fixes
Component/s: Records Management, Share Extensions and Customisations
Affects Version/s: 5.2.1, RM 2.5.2
Fix Version/s: RM 2.5.3

Type: Service Pack Request
Reporter: Marc Bynum Assignee: Closed Bugs (Inactive)
Resolution: Fixed Votes: 0
Labels: triaged
Remaining Estimate: 1 hour
Time Spent: 2 days, 1 minute
Original Estimate: 3 days

Bug Priority:
Category 2
ACT Numbers:

00914343, 00934749

Premier Customer:
Sprint: Nightwing 27 - Condiment King
Work Funnel End: 2018-03
Story Points: 3


In Alfresco-One 5.1.2, sitePresets.SiteServices  worked with Records Management. This is a feature that is both desirable and necessary to some organizations.  The simple addition to share.header.get.js no longer works in 5.2.1 with RM 2.5.2


var siteService = widgetUtils.findObject(model.jsonModel, "id", "SITE_SERVICE");
if (siteService && siteService.config)
  siteService.config.additionalSitePresets = [{ label: "Custom Preset", value: "CUSTOM" } ];

This functionality is documented at https://docs.alfresco.com/5.2/references/dev-services-site.html and https://docs.alfresco.com/5.2/tasks/dev-extensions-share-tutorials-custom-share-header-menu.html.

Records Managment 2.5.2 appears to overwrite share.header.get.js no matter in which order the extensions are run.  In order to run both custom site presets and Records Management, the developer MUST modify the Records Management extension at share.hearder.get.js to unknown ends to apply additionalSitePresets.  This is not a supported operation and reduces the usability of the Alfresco Content Services. There should be a way to modify the Records Managment Extension to account for custom site presets.  The attached Maven All-in-one build demonstrates this issue in a simple example.

Steps to reproduce:

  1. Build the attached maven project (All-in-one with RM and a very simple customization)
  2. Login to Alfresco and Check Site/Create site and ensure Records Management is installed
  3. Custom Preset module should be installed, as well, however, note that it is not.loading.
  4. Navigate to http://localhost:8080/share/page/modules/deploy and remove RM Modules.
  5. Navigate back to "Create Site" and select the site type pull down.  Note Custom Presets exist
  6. Return to http://localhost:8080/share/page/modules/deploy and add the RM Modules, again.
  7. Navigate back to the "Site/Create Site" pull down and select. 


Expected Result:

Both Custom Preset and Records Management Sites should be displayed.

Actual Result:

Only Records Management is visible.  

This method was suggested here:  





Comment by Build And Packaging (Inactive) [ 20-Feb-18 ]

Richard Smith mentioned this issue in a merge request of records-management/records-management:
'MNT-18543: Rewrite siteService.config additionalSitePresets and…'

Generated at Tue May 18 05:12:56 BST 2021 using Jira 7.13.15#713015-sha1:7c5ddd2c3e1709974ae9c48c17df8edd3919fe2c.