* 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
* all users that had 'write' permissions on a document when it becomes a record continue to have 'file' on that record.
* these users also have EditMetadata capability
* this include the owner of the document at the time it was made a record
* extended 'read' permissions for created records continues to work in the same way
* added an extended permission service with additional method to get the writers of a node .. configured and implemented as an extension to the core and held in the RM AMP (could be moved down at a later stage if appropriate)
* patches updated
* unit tests updated (and fixed)
* content model updated to more generic 'ExtendedSecurity' aspect with writers property
* service generalised as an ExtendedSecurityService with appropriate method changes
* mandatory parameter no longer mandatory in create-record action .. fixes issues seen in unit tests and UI
NOTE: due to the nature of this change any db's created on an earlier 2.1 dev build will need to be reset .. going from 2.0.1 onwards will, however, be fine.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@46270 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
* build scripts updated so generated eclipse projects don't double up dependancies
* demo code removed entirely
* permission service override replaced with extended class based on updated core permission service implementation
* unit test juggling
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@44009 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
