* edit disposition action now works
* associated capability improved to only show action when disposition date available to be updated!
* issue became apparent because the available disposition properties don't always make sense for a folder level disposition (eg: file date)
Disposition properties are context sensitive:
* UI dynamically pulls list of disposition properties based on disposition level and disposition action
* WebScript added to retrieve disposition properties based on context
* Disposition properties spring context indicates excluded actions and disposition level relevance
* Added Created Date as disposition property for folder level disposition
* Cutoff Date no longer shows as disposition property option for cutoff action
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/V2.0@38394 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* migrated record series, despite extending record category, don't have the record category custom properties shown in the UI
* record series is labeled as 'deprecated' in the edit custom properties console
* some re-org of 'compatibility' code
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/V2.0@37271 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* Added 'ListAdmin' unassignable capability
* Fixed up introduced issue with console permissions (last minute change to JS caused all capability checks to fail on management console .. for some reason I didn't recycle and spot untill today!)
* Can not undeclare a cutoff record (another small issue spotted today)
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/V2.0@37126 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* added web script to retrieve the capabilities of the current user, either based on a provided node or the file plan otherwise.
* updated RM console to use new webscript, was using role webscript which doesn't accurately show what a user can do, nor include unassignable capabilites that can be used for convenience.
* added unassignable, composite capability 'AuditAdmin'
* protected audit console with new capability, this means users with only DeleteAudit (for example) can now see the management console.
* related to RM-186
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/V2.0@37057 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* automatically delete assiciated roles (ie groups) when a file plan (ie the RM site) is deleted
* add the user that created the RM site into the Records Administrator group (a convenience improvement)
* fixed knock on issue with getting FilePlans and ignoring those in the archive store!
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/V2.0@36749 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* By passed issues caused by changing AMP name ... seems the component registry isn't updated so some are re-run, potentially causing issues
* Added compatibility class ... is referenced by a 1.0 custom model .. also gives us a slot if other issues arrise .. may move some of the other compatibility code in here if I get time
* Tested upgrading from V3.4.x to V4.0.1 with RM 2.0
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/V2.0@36597 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
* RM-218: Frozen records can be deleted (only the valid actions show when a record is frozen)
* RM-315: It's possible to edit metata data for frozen record (it's not and the actions no longer show)
* RM-347: Its possible to freese undeclared record (yes it should be and the actions to support this have been enabled)
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/V2.0@36389 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
* fixed up add record web script as it was using a admin only web script
* extended rm meta-data web script to support above
* EditRecordMetaData capability missing for composite Update and UpdateProperty capabilities
* EditNonRecordMetaData capability takes into consideration whether the user is the owner or not
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/V2.0@36180 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* Updated implementation of form filters to include custom properties and custom record aspect properties
* Overide FormUIGet web script implementation to include custom properties (and custom record meta-data aspects) despite now using a 'show' strategy for the form defintions.
* Added a RM 'kind' config evaluator. This allows us to provide a form definition for the different 'kinds' of RM artifacts which are automatically merged with the core form related to the content type. This is especially useful for records as we can now support the correct display of extended content types and content with additional aspects.
* Added rm metadata web script to support the kind config evaluator.
* Re-factored all form definitions into 'kinds' and core types where appropriate ... means implementors can extend our core RM types and still have the correct Rm information displayed whilst defining their own forms for their new types.
* Separated out the DOD specific form parts for the record kind.
* Non-electronic document form added (and auto-includes record kind form)
* relates to RM-269 and RM-137
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/V2.0@36154 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
