* ReportService added ... will be used to consolidate the various reports withing RM (specifically those needed for DOD complicance)
* Base and declarative implementations of report generators added
* Destruction report configured with place holder implementation (still need to do name generation, meta-data and final template)
* Report model added, with destructionReport type defined
* FileDestructionReport capability added (and capability patch bean updated)
* Repository action added to file destruction report
* UI configured to show 'file destruction report' action .. (creates a report and files it as an unfiled record as the destruction report type)
* fixed up destruction capabilities and actions (capability to destroy record regardless of its current dispostion state did not work)
* added "AtLeastOne" composite capability condition
* TODO destruction report template, name and meta-data generation
* TODO patch to add report template structure to rm data dictionary area
* TODO start refactor of existing reports including transfer, accession, userRights, filePlan and audit!!
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@52562 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* move candiate methods into FilePlanService
* deprecation of RMService methods
* remove all deprecation warnings from code
* update filePlanService unit tests
* remove all other spurious warnings from RM code
* a couple of performance enhancements in the bowls of the capability evaluation code
* first pass at parametising RecordsManagementAuditService with file plan (so capability evaluation had a tangable reference)
* fix up unit test failures and other fall out from refactors
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@52504 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* New action conditions added:
Is classified
Is cutoff
Is frozen
Is record folder closed
Is vital
Has Disposition Action
Is kind
Is Record Type
* Action conditions dropdown list on the edit rule page reorganised
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@51812 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
* add additional user/group management methods to FilePlanRoleService java API
* add file plan retrieval methods to FilePlanService .. including retrieving file plan node reference from RM site id
* deprecate file plan retrieval methods on RecordsManagementService
* add FilePlanService unit tests
* refactor role web service API implementations to allow the file plan (or rm site) to be specified
* GET roles can optionally include information about the assigned users and groups
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@48438 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
