99087: Upgrade Alfresco version to 4.2.4.6
99088: RM-2026: Unable to complete historical records when mandatory meta-data missing
99089: Merged HEAD to V2.2:
89735: RM-1677- No items error for RM Admin if record was declared from moderated/private site
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/V2.3@112663 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* record metadata aspects are now configured via spring and includes which file plan type they are relevant for
* added 'unit test' structure .. for 'real' unit tests, ie anything that doesn't load the application context
* included Mockito, new source location and unit test suite into POM
* added unit and functional tests for feature (server)
* refactored accordingly (webscripts, UI, etc)
* visual test of UI .. automation tests to follow
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@63013 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
* refactored audit events to be spring configurable, registerable beans
* adjusted how actions are audited
* added missing action I18N labels
* adjusted how audit events are stored against the transaction so that more than one is recorded per transaction (previously it was the last event to happen that was recorded)
* unit test running and share tested
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@54678 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
RM-642: A records manager can create a rule with a "Is Declared" condition
RM-641: A records manager can create a rule with a "Is Filled" condition
RM-638: A records admin can choose from a specialised list of RM relevant conditions when defining a records rule
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@48587 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* RM actions can be configured to allow parmater level substitution
* Paramater processor component added .. resposibile for processing parameters of an RM action and selecting the correct processor
* Parameter processor framework added .. new processors can be sprung in using the usual pattern
* 'node' processor added .. allows simple property value substitution based on the actioned upon node
* 'date' processor added .. allows simple date value substituation
* 'message' processor added .. allows message bundle value substitution
* an example substitution parameter could be .. "/${message.my-company.name}/invoices/${date.month.short}"
* fileTo action is configured to allow parameter substitution .. with the relative path and auto create features as well it is possible to define a rule that creates records folders based on a simple creation strategy .. for example always file into a record folder for this month
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@47262 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* rm actions can be applicable to only certain 'kinds' of RM artifacts
* when retrieveing with context, RM actions are only applicable to RM artifacts and vice verca for DM objects
* delegate RM action available to be configured against existing DM actions
* unit tests
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@45699 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* actions and capabilities no long linked
* protected aspects and properties can be configured in their own right
* protected model security service added
* action implementation refactored accordingly
* capability implementations refactored accordingly
* unit tests
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@44229 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* moved RM tests into separate folder structure
* updated Gradle scripts with test source locations and dependancies .. 'gradlew test' will now attempt to execute the unit tests (even if they fail!)
* eclipse project dependancies updated so unit tests execute within the RM eclipse project
* TODO get the unit tests working reliabily! (still lots of refactoring of old tests to do)
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@35093 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
