* an assignable capability
* performs as the missing 'filling' capability
* also added a unassignable capability for HideRecords
* ensures that extended writers .. ie users that have temporary filling permission on records .. can not then fileTo or reject records
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@46408 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
* means search and other navigation paths work correctly
* will allow the navigation of the unfiled container via other UI's and API's much easier
* created the file plan service
* methods relating to the unfiled container now encapsulated in the file plan service
* TODO move many of the methods in the records management service into the file plan service .. with the ultimate aim of deprecating the catch-all records management service!
* delt with fall out from changes
* relates to RM-583
NOTE: you will need to recreate any db's previously created on the 2.1 development branch ... any pre-2.1 will be fine and patch correctly.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@45823 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
* final deprecation of recordsManagementSecurityService
* origional interface and implementation moved to compatibility area
* deprecation context added
* FilePlanPermission service added to handle file plan permissions
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@44829 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* file and setup folder action removed in favour of services
* disposition action methods consolidated in disposition service
* vital record action methods consolidated in vital record service
* unit test updates
* other code fallout
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@44783 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* fleshed out unit tests for record service
* fixed up a couple of issues when creating records
* unfiled record API integrated into the Record Service
* investigated moving filling API from actions into service (roughed out API)
* updated create record action
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@44403 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* we don't need to evaluate the capabilites, just need to know if the user 'has' the capability
* added ebable/disable
* disabled for now since code refactor is complete, but we need to think some more about what (and why) some properties and aspects are protected
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@44230 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
