59208: RM-1115: Manage Rules action is available for a Frozen folder - Added condition that manage rules isn't shown for frozen folders
59343: RM-1114: 'Loading the Document Library' message is displayed on a New Rule page in RM Site - Added appropriate message.loading properties to all languages for rule-details.get and rule-edit.get where this message is used
59361: RM-1105: Adding the RM module causes exceptions when listing the existing audit applications through the audit webscript - Added a try/catch for a ClassCastException around the check to see if the returned object contained a PROP_HOLD_REASON in the RMAfterInvocationProvider. The reason for this is that the containsKeys method will throw a class cast exception if we attempt to see if the keys contain an instance of QName if the returnedObject instance is a TreeMap containing strings as is the case when listing the audit applications through the RESTful interface.
59510: RM-1087: Increase default max number of site pages to 5 instead of 3 - Increased default maximum number of sites pages to 5 in rm-share-config.xml. This threw up an issue in the code that adds the RM Console widget so fixed that too. Important test case for this are that the number of widgets added to the site are smaller than, equal to and greater than the maximum displayed to ensure that the code adding the RM console is fully exercised.
60429: RM-1162: CLONE - Alfresco 4.2.1 could not start with RM module
* see MNT-10259
60430: RM-1162: CLONE - Alfresco 4.2.1 could not start with RM module
* see MNT-10259
* missed files
60431: RM-1162: CLONE - Alfresco 4.2.1 could not start with RM module
* failing tests
* see MNT-10259
60478: RM-1174 (Unable to view record details)
60698: RM-1175: Internal Error on details page of category/folder/record
60699: RM-1177: User's name link on User Rights Report page directs to Admin Console instead of User Profile Page
60700: RM-1176: Couldn't load email mappings
61227: RM-1164: RM 2.1.1 core language bundle refresh
62414: RM-1165 (RM 2.1.1 translation into Simplified Chineese)
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@62565 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* RM-1178: Add DOD site and file plan types to DOD specific content model
* RM-1179: Extend create site dialog to set allow creation of DOD compliant RM site
* RM-1180: Create a patch to update all existing file plans to be, by default, DOD compliant
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@60943 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
RM-1125 (RM user can delete a folder within the unfiled records area)
RM-1126 (RM user can edit the meta-data of a folder within the unfiled records area)
RM-1127 (RM user can view the details of a folder in the unfiled records area)
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@60639 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
RM-1125 (RM user can delete a folder within the unfiled records area)
RM-1126 (RM user can edit the meta-data of a folder within the unfiled records area)
RM-1127 (RM user can view the details of a folder in the unfiled records area)
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@59986 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* remove DOD meta-data from record aspect
* create dod record aspect in dod model to contain dod specific meta-data (modelled as record mate data aspect so can be added manaually and UI reacts accodingly without modification)
* automatically add dod record aspect to record when created (maintains status quo for the time being)
* allow groups to be automatically added to form UI template when record meta-data found on record (DOD meta-data automatically displayed and editable if present)
* add simple module patch frameowrk so RM patches going forward are module schema based (so order and application is predictable)
* fix up existing patchs (pre 2.2) so basic order is guarenteed
* add patch for DOD data reshuffle
* general restructuring of patch configuration and implementations for clarity
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@59972 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* remove DOD meta-date from record aspect
* create dod record aspect in dod model to contain dod specific meta-data (modelled as record mate data aspect so can be added manaually and UI reacts accodingly without modification)
* automatically add dod record aspect to record when created (maintains status quo for the time being)
* allow groups to be automatically added to form UI template when record meta-data found on record (DOD meta-data automatically displayed and editable if present)
* add simple module patch frameowrk so RM patches going forward are module schema based (so order and application is predictable)
* fix up existing patchs (pre 2.2) so basic order is guarenteed
* add patch for DOD data reshuffle
* general restructuring of patch configuration and implementations for clarity
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@59943 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* merges from previous branches are now possible without tree conflicts
* added back missing commits when structure was changed (r59445, r59446) .. see RM-765
* updated Maven POM's to use existing code structure
* NOTE: r59454 and r59473 may have been missed in this update .. will go back and re-add
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@59491 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* Created a base report action and splitted the file report action to transfer report action and destruction report action, so that capability checks can be run for those actions separately and each action can pass additional properties to the report template model
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@58444 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* added behaviour bean and method annotations .. allows the simple defintion of methods as behaviours, simplifies code and provides a way to report on the registered behaviours in the future
* moved and consolidated some of the behaviours into classes based on the RM object model .. with behaviours in one logical place it should reduce issues with unpredictable behaviours and help maintenance
* TODO more consolidate still needed
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@58120 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
