52115: RM-732: CLONE - "caveat" functionality of the (dod5015) Records Management Module is not cluster-aware
52262: RM-757: Permission confusion after upgrade from 1.0
52264: RM: Unable to set list of values after migration from 1.0->2.0.3
52294: RM-769 (Impossible to add access for several values)
52340: RM: Saved searches where not being upgraded correctly
* searches resaved on upgrade (to account for updated model)
* searches are public by defalut
* relates to RM-758
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@52341 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
51415: Merged DEV/DODRECERT TO BRANCHES/V2.0:
* 50932: RM-741: Allow category and folder id to be editable upon creation.
51418: Merged DEV/DODRECERT TO BRANCHES/V2.0:
- r50934: RM-742: Search sort order now works as expected
51419: Merged DEV/DODRECERT TO BRANCHES/V2.0:
- r50953: Creating an RM site was not possible (ref RM-742)
51420: Merged DEV/DODRECERT TO BRANCHES/V2.0:
- r50970: RM-735 (DOD Recert: Bugs on the "Edit Custom Metadata" page)
51421: Merged DEV/DODRECERT TO BRANCHES/V2.0:
- r50975: RM-736 (DOD Recert: Bugs on the "List of Values" page)
51423: Merged DEV/DODRECERT TO BRANCHES/V2.0:
51425: Merged DEV/DODRECERT TO BRANCHES/V2.0:
- r51082: RM Audit
* improved display so it's easier to see what's going on
* RM 744: audit user creation
- r51095: RM-738 (DOD Recert: Add events and properties to the "Audit" page)
- r51099: Fix upgrade issue
- r51108: RM-745: Simple support for event and property filtering on audit
- r51134: Upgrade issues
* added patch to fill in missing file plan root node reference
* default site id set when retrieving saved searches
- r51212: RM-746: Space in the property name
51426: Merged DEV/DODRECERT TO BRANCHES/V2.0:
- r51218: RM-747: Search for undeclared records results in exception
- r51219: RM-748: Editing a disposition schedule did not work for a non admin user
- r51220: RM-749: Fixed Accession Report
51504: RM: Fix build
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@51946 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
48720: RM-657: Items section is not displayed on Start Workflow page when RM installed
48749: RM-664 (Not possible to edit event without changing the name)
48772: RM-664 (Not possible to edit event without changing the name)
49445: RM-675: CLONE - Document Details page: 'Comment' link is not working
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@51945 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
More check-in for bug fixes from developer test.
* Fixed issues for "Has Disposition Action", "Is Kind" and "Is Record Type".
* Added transaction or security context around the contents in RecordsManagementActionConditionEvaluatorAbstractBase.init() so that action conditions can use RecordsManagementActionService (the capitalised one) in Spring config.
* Removed "File Plan" from Is Kind action condition dropdown list selection.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@51941 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
* Merge HEAD to DEV/DODCERT
- r43798 RM-552 (Add 'Manage Permission' action to file plan toolbar)
- r43859 RM-552 (Add 'Manage Permission' action to file plan toolbar)
* Changed the icons
- r43863 RM-552 (Add 'Manage Permission' action to file plan toolbar)
* Changed the existing ManageAccessRights capability and reusing it
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/DEV/DODRECERT@50933 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* add move behaviour to file plan permission service .. inherited permissions are adjusted, any set directly on the record are kept
* added missing unit test for file plan permission service
* test add/remove
* test record move
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@49535 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* capability for inplace user no longer defined by dynamic authorities (inheritance was incorrect)
* default roles added to allow capabilities of reader and writer inplace users
* record permission inheritance broken .. was on the todo list for a long time, but needed to be done now to ensure the correct inplace permissions where evaluated at the record level
* unit tests
* TODO ... patches to migrate to 2.1 for new roles and record permission inheritance change
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@49215 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* record service extended with isPropertyEditable method .. indicates, based on the capabilities of the current user and the nature of the property, whether it can be edited
* the record service monitors record aspect property updates and throws ModelExceptions if a user tries to update a record or non-record property if they don't have the appropriate capability
* form filter updated to protect record properties the current user may not be able to edit
* unit tests
So what does this all mean?
It means we can control the write permissions of individual properties on a record based on capabilities. In this case we slice the capability to edit a record in two .. you can either edit the content properties (ie the normal meta-data) or the record properties .. or both of course!
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@49041 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* RM-631 (The records management team can create a rule to request information about an undeclared record)
* RM-632 (The records management team can use an UI action and custom UI to start a "request for information" workflow about an undeclared record)
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@48854 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* moved policy implementations out of RMEntryVoter and into separate classes
* rather than being a hard coded list, policies are now registered via spring allowing others to be easily added
* re-arrange some of the support implementation
* RMEntryVoter is now significantly smaller and most of the logic that was once encapsulated in here is spread over supporting classes and services
* TODO .. need to review policies and determine which are appropraite .. much easier to do now!
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@48815 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* consolidate the groups capabilities are within (rename and try to simpify)
* 'deprecate' classification related capabilities into the dod specific package .. these capabilities didn't do anything so will be removed until such a time comes when we consider classified records.
* remove legacy unit test .. becomming too difficult to maintain and is covered by newer tests
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@48750 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* refactor how we extend the rule's UI
* existing rule's UI is left uneffected .. config no longer needs to be overriden .. so custom config will not effect RM
* web scripts overriden to use RM specific action and condition UI config
* actions and conditions not added to general pool of those available from the rules service ... means no filtering is required on the main UI
* module filter used to override component and redirect to the overridden webscripts
* server side support of records management conditions added
* isFiled and isDeclared conditions added
* TODO .. still a couple of lose ends to tie up
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@48659 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
