* ensure all the record information is removed from a rejected record (seeing issue with ID being reset)
* rejected records are ignored by the create record action
* note: there are still some features we need to add to expand the rejected records use case
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@48064 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* added some debug to help when trying to diagnose permission deny issues
* system folder created by the rule service was not a file plan component, so permissions where failing when accessing them as a pure RM user
* file plan component added as required
* ManageRules capability needed a filling condition (this may cause the manage rules button to be disabled .. this is another issue and will be addressed shortly .. work around by assigning user filling on file plan for now)
* added extended method security for rule service .. currently defaults to alllow all, but will need to be closed down with ManageRules capability
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@47624 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
* provides methods to allow code to be run as the rm admin user and to retrieve the rm admin user name
* all unit tests now run as rm admin user by default
* default bootstrap user name configurable (as well as pwd)
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@46751 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* this allows code to be 'runAsRMAdmin' .. rather than having to use System (remember 'admin' isn't nessesarily an rm admin)
* will give us the option to run rm rules as rmAdmin (this may be the default case for the time being and later part of the configuration of the rule)
* will also allow us to add RM admin level security to methods (for example can only create a role if you are an rm admin)
* rmAdmin user has global RM admin rights to all file plans (when we go to multi-file plan support)
* rm user bootstrapped via module 'patch' .. this will execute on existing V2.1 db's
* filePlanRoleService unit test (was missing! .. my bad!)
* relates to RM-596 (this rule needs to be executed as the rm admin)
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@46749 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* 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
