41707: RM: Transparent records management prototype WIP
* Create Record service and refactor
* Add 'createRecord' method that preserves origional location(s) of the content
* Add content readers information to record on extended security aspect
* Experimental dynamic authority
* DM action to 'create' record
* Behaviour and methods to create and get new record container
41708: RM: In-place filing prototype WIP
42063: RM: Inplace filing prototype
* extension of seciruty service to allow management of extended readers
* extended reader maintained within file plan hierarchy
* support ready for removal (ie move) and overlapping of readers in hirearchy (maintained in reference counting map)
* general rename to "Unfiled Records" rather than "New Records"
* File plan unfiled records filter
* Unit tests
* Correct permissions on created unfiled container (file for admin as per file plan root)
* record readers dynamic authority applied to file plan components on bootstrap and creation
42374: RM InPlace Prototype:
* permission mapping improvements ... allows filling and declaration of unfiled records
* actions of 'records' in doc lib are shown as restricted rm list
* "Record" banner is shown in doc lib if content is a record (this differs from the normal record view where the undeclared status is shown, this isn't relevant for a content user)
* linked to many record folders indicator not shown unless it really is linked to many record folders
42700: RM Prototype:
* stoppped hidden RM actions from appearing in UI
* added file record action (TODO run-as RecordsManager and make applicable via aspect)
* added hook points to allow customisation of Rule UI and customised for file record action
43030: RM: In-place prototype
43238: Rule editing fixed
43332: Implemented a DeclareRecordAction so that a rule can be setup for a folder and a user can declare a record just uploading a file (in a collaboration site) into the folder.
43348: DeclareRecordAction: The actioned upon node should be a record no need to create a record from the actioned node. If it is not a record an error should be thrown. If a user wants to create and declare a file as record a composite rule can be used.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@43934 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
39658: RM-469: Modified date is updated for all items in File Plan at the same time
41343: Merged V2.0-BUG-FIX to V2.0 :
39590: RM-452: RM seurity context will break core Alfresco if Alfresco's public services change
39591: RM: Removal of System out's and replace with logging.
39592: RM: Update properties of 2.0.1 build
40344: RM-477: RM 2.0 does not work with SOLR
* first pass at supporting SOLR in RM2
* currently requires reimplementation of permissionServiceImpl due to visibility of methods and member variables
* job execution delayed to try and prevent start up errors
* fetchSOLR task added to gradle to retrieve SOLR zip from Maven (could do with some scripts to help with setup for module)
* TODO more testing and refinement of solution
40383: RM: Fix unit test
40656: Updated ReadMe.txt
40696: RM-439: Folders have no File to... option
40778: RM-434: The user has all rights for audit once "Access Audit" capability is added to him
40784: RM-482: RM .classpath files have local library references
40785: RM: Remove .settings dir for Eclipse projects
* See RM-482
40786: RM: Set svn:ignore for generated eclipse project files
40800: RM-434
40904: It was not possible to edit/delete a custom meta data
40920: Disabled the delete button for custom meta data
40948: RM-438: Custom metadata fields and Special Types aren't available in Email Mappings
41021: RM-438: Custom metadata fields and Special Types aren't available in Email Mappings
* ensured the 'group' information was being passed to property-menu (so the custom and dynamic record meta-data is available)
* also tweaked audit in the same way
* removed code to add custom meta-data props as no longer needed
41023: Merged HEAD to BANCHES/V2.0-BUG-FIX:
40944: Adds Spanish RM translation
41263: RM-492: RMMetaDataGet: Namespace prefix Alfresco is not mapped to a namespace URI
41305: RM-495: Search for Workflow Group Assignee does not work
41307: RM-494: Access when changing type in Records Management 2.0
41403: RM-496: Incorrect behavior on Move action
41638: RM: Spanish translation
42412: RM-499: Collabarator can add categories when they should not be able to
42413: Fix up unit test.
42506: RM-507: Incorrect RM module version is displayed after the module installation and during the startup
42555: RM-501: Incorrect behaviour on Move To Action
42558: RM-503: Record Search - Category is not found by VitalRecordReviewPeriod
42564: Merged modules/recordsmanagement/BRANCHES/V2.0-BUG-FIX to modules/recordsmanagement/BRANCHES/V2.0
42532: RM-510 (CLONE - RM Email Mapping tool behaves strangely)
42567: Merged modules/recordsmanagement/BRANCHES/V2.0-BUG-FIX to modules/recordsmanagement/BRANCHES/V2.0
42539: RM-506 (RM Console - Audit - Some Audit Events are displayed incorrectly.)
42569: Merged modules/recordsmanagement/BRANCHES/V2.0-BUG-FIX to modules/recordsmanagement/BRANCHES/V2.0
42527: RM-240 (In the RM Console: Can add two events of the same name)
42602: RM-500: SOLR: "No items" message after complete Transfer action
* filtered non-existant node from search results
42603: RM-502: SOLR: Search by Records properties doesn't work
42633: RM-512 (RM actions are odd after renaming a category/folder/record)
42634: RM-511 (Repository Descriptior (originally installed) is broken if RM installed)
42645: RM-507: Incorrect RM module version is displayed after the module installation and during the startup
42673: RM-520 (RM Site - File Plan - 'Show Folders' and 'Sort' icons show incorrect pop-ups)
42675: RM-521 (RM Site - File Plan - 'Show Folders' link is incorrect)
42682: RM-515 (Incorrect labels for categories, folders and records on Repository Browser page)
42697: RM-517 ('Import' button is enabled in a closed folder)
42701: RM-517: 'Import' button is enabled in a closed folder
42707: RM-519: RM 2.0.1 NPE ERROR on startup
42749: RM-512 (RM actions are odd after renaming a category/folder/record)
42777: RM-514: SOLR throws several errors during the startup
42778: RM-529: Not possible to delete reference from target record
42779: RM-523: Installation: Impossible to install RM module without -force option
42780: Re-adding custom bubbling js file that has IE7 specific fixes.
42794: There is no need to override the documentlist.get.properties. The rm specific properties have been moved to rm.properties. In doing so we'll prevent missing "standard" labels
42795: No need to keep documentlist.get.js in the rm module. There are no changes in this file
42877: We cannot delete documentlist.get.js. It is needed for the file plan site. This file does not replace the original file. The paths are different.
42897: RM-452: RM seurity context will break core Alfresco if Alfresco's public services change
* ensure the '*' definition is at the end of the updated value
* add missing method definitions
42898: RM-522: Disposition actions for record are not available for non-admin users
42908: RM-526 (Incorrect pop-up for EXIF icon)
42909: RM-531: Impossible to declare email record
42911: RM-533 (RM AMP doesn't work with latest community build)
42940: RM-527 (Simple view is not correct on the File Plan page - thumbnails are displayed instead of filetype icons)
42983: RM-528 (It's possible to create relationship with the same name as already exists)
43482: RM: add -force parameter to build scripts
43486: Merged V2.0-BUG-FIX to V2.0 :
41757: RM-472: Spelling errors in Management Console (Events)
42505: RM-462: Spelling errors in Edit Disposition Schedule
42527: RM-240 (In the RM Console: Can add two events of the same name)
42532: RM-510 (CLONE - RM Email Mapping tool behaves strangely)
42539: RM-506 (RM Console - Audit - Some Audit Events are displayed incorrectly.
42776: RM-463: Tooltip text inconsistent on Edit Disposition Schedule page
43714: Merged V2.0-BUG-FIX to V2.0 :
43623: RM-541 (Error shown in firebug when the details page of a record is open)
43661: RM-550 (JS Error while declaring a record)
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@43758 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* extension of seciruty service to allow management of extended readers
* extended reader maintained within file plan hierarchy
* support ready for removal (ie move) and overlapping of readers in hirearchy (maintained in reference counting map)
* general rename to "Unfiled Records" rather than "New Records"
* File plan unfiled records filter
* Unit tests
* Correct permissions on created unfiled container (file for admin as per file plan root)
* record readers dynamic authority applied to file plan components on bootstrap and creation
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/DEV/INPLACE@42063 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* dynamic authority set ReadRecord permission on new record and ViewRecord capability on containing file plan
* dynamic 'Record Readers' authority working correctly (checking whether current user is contained in the users/groups snap shoted as readers when the document was made a record)
* unit test showing document in collab site being made a record and the existing collab user having record read permissions without being added to the RM site or given an RM role.
* this check-in is sufficient to demonstrate that collaboration users can create records and view them without having to introduce any form of noticable mapping between the RM and Collab sites. (relates to RM-485)
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/DEV/INPLACE@41708 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* Create Record service and refactor
* Add 'createRecord' method that preserves origional location(s) of the content
* Add content readers information to record on extended security aspect
* Experimental dynamic authority
* DM action to 'create' record
* Behaviour and methods to create and get new record container
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/DEV/INPLACE@41707 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* RM-336: Impossible to create File Report for transferred object
* RM-170: Not successfully complete Transfer action
* RM-210: Assession disposition action does not disappear after event completion
* RM-224: Script error when add Disposition Transfer Step if user doesn't have access to any Transfer Location
* RM-346: Incorrect list of actions for transfered Folder or Record
* RM-358: A folder isn't displayed in Transfers without without reloading the page.
* RM-331: Audit is removed from Transfers and Holds
* Also the transfer and accession capabilities are refactored to work correctly.
* Transfer, accend, and relevant complete actions all correctly react to the different capability assignments.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/V2.0@36528 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* Refactored server side unit tests (exposed at least one bug and shows that the event and property filters are still not working)
* Fixed up admin and object audit views (formatting is still terrible, but it's functional)
* Will close out the related issue, since formatting and other issues are covered by other bugs.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/V2.0@36483 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* Added Record Folder, Record Category and composite Move capabilities (all private and based on exisiting capabilities)
* Added RM UI actions for record, folder and category move wired up to new capabilities .. this means the UI actions correctly reflect the capabilities of the user
* Unit tests
* Started to move the capabilitiy spring def's into logically seperate files
* Rewrote origional RecordsMove capability (replaced with spring config)
* Added TargetCapability configuration to declarative capability implementation .. provides a way to evaluate capability when a target node reference is being taken into consideration
* Added title and description to declarative capability (for future use)
* Removed unwated 'old' doclib overrides (where confussing the issue)
* Clean up the security service which was duplicating methods now found on the capability service
* Remove capability set support ... old work around used before updated evaluators where used
* Fixes RM-203, RM-328, RM-165, RM-204 (and possibly some others I've yet to find!)
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/V2.0@36338 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* refactored the way disposition properties work
* now additional disposition date properties are sprung in and registered in the disposition service
* each disposition property bean looks after updating the disposition asof date when the date property changes
* defaults to null date if can not be calculated
* unit test for new method and this issue
* also updated build scripts to successfully run unit test .. will gradually add in other unit tests as their reliability is improved
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/V2.0@36222 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* Edit details Ui action now reflects user's capabilites correctly
* Fixed up a couple of behaviours that don't execute when non-admin user (run as system user since admin may not be rm admin)
* Transfers not appear in docLib filter correcetly
* File UI action now reflects the user's capability correctly.
* Renamed 'group' capabilities to 'private' as this more accurately reflects what it means.
* Added composite capability implementation ... allows us to futher consolidate some of the edge cases and will allow us to break down further some of the existing capabilities .. this makes is much easier to see and understand exactlly what each capability is doing
* Refactored current 'group' capabilities .. replacing with pure spring config where appropriate .. much clearer what they are doing (and fixed up where they wheren't doing exactlly the right thing)
* Moved the remaining group capabilities impl's with the other capability impl's .. we are now down to 8 custom capability implementations .. down from 50+ .. and these havily borrow from the base classes where they can ... makes maintenance MUCH easier!
* more unit tests
* used new 'private' capability technique to break up FileRecord capability ... it's now clear what it is doing and could be corrected easily
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@35350 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* Fixed up issues seen during QA security knowledge transfer session
* hard coded "Read" evaluation in DocLib js is overridden in RM to account for "ReadRecord" ... not ideal solution but no other option for the moment
* property pages now show for non-admin users
* actions on toolbar showing and hidding correctly when capabilities missing
* other actions showing and hiding correctly when capabilities missing
* view details UI action to capability link now working correctly
* some unit test monkeying
* gradle scripts have 'explodedDeploy' taget which does deploys content of AMP (or at least what would be the contents of the AMP) to the exploded web apps ... speeds up dev time heaps!
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@35251 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* Removed web script tests dependancy on DOD test data
* refactor base RM test and placed common utils in common class
* base rm web script class created
* unit tests refactored (still some work on the older tests required)
* junit conflict resolved
RM Bug Fixs:
* user rights view working again
* fix from Erik so RM admin console works
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@35190 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* moved RM tests into separate folder structure
* updated Gradle scripts with test source locations and dependancies .. 'gradlew test' will now attempt to execute the unit tests (even if they fail!)
* eclipse project dependancies updated so unit tests execute within the RM eclipse project
* TODO get the unit tests working reliabily! (still lots of refactoring of old tests to do)
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@35093 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
