* FileUnfiledRecords and RejectRecords are now assignable capabilities
* by default Admin, Records Manager, Security Manager and Power User have them
* they can be added and removed from custom or default roles via the management UI
* capability patch updated accordingly
* extedned get roles ReST API to include/exclude system roles
* In-Place Reader and In-Place Writer roles capabilities are configurable again, but their users and groups are not (as intended)
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@55935 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
Moved all work of RMv2ModelPatch into the RetryingTransactionCallback. RetryingTransactionHelper set to create new thread.
Add RetryingTransactionHelper to RMv2FilePlanNodeRefPatch. Move all of the work of the patch into the callback. Helper creates new thread.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/V2.0.1.x@55708 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* destroy always capability has been deprecated .. it's highly confussing and isn't nessesary when delete is available
* can be configured back in easily if required, but wasn't working in 2.0 so highly unlikely to be needed
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@55372 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
RM-923 Several actions don't trigger the updated rule
RM-925 The updated rule is triggered several timce by complete/undo event, cutoff/undo cutoff
- Added dispositionActionDefinition to the list of types to be ignored by rule triggering just so that 'edit disposition steps' will not cause update rules to be triggered to avoid confusion.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@55313 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
- Added a new Spring config property 'auditedImmediately' to work alongside 'auditable' property to indicate that the action should be audited immediately rather than after transaction commits. The default value of 'auditedImmediately' is false unless it is specified as true by individual action in rm-action-context.xml.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@55259 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
- Just tidied things up a little. Added the following override so that by default it is audited immediately and the audit entry isn't removed. This means a lot of the calling clients don't need to understand or define the last two properties.
@Override
public void auditEvent(NodeRef nodeRef, String eventName, Map<QName, Serializable> before, Map<QName, Serializable> after)
{
auditEvent(nodeRef, eventName, before, after, true, false);
}
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@55256 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
- Specified a list of properties in Spring's configuration to be ignored by audit.
- If an audit entry ends up with no changes in properties then we discard the entire audit map altogether. Currently this applies only to 'Update RM Object' events as other events still require to be audited even if there are no property changes.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@55219 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
* it now valid for admin to have access to the file plan
* rmadmin is still created and always has admin rights to file plans, but by default is created with a random password
* admin has permissions to reset rmadmin password if administration of RM file plans needs to be delegated
* rmadmin name I18n'ed
* rmadmin patch and creation code updated
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@55205 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
- To eliminate multiple audit maps from being generated when events with the same name are required to be fired multiple times in the same transaction, the code checks on existing auditedNode stacked for the same combination of nodeRef and eventName. If there exists such an auditNode, update its 'after' properties with the latest set of properties and leave its 'before' properties unchanged so that it retains the original set of properties. The first 'before' and last 'after' will be diff'ed when comes to building the auditMap later when the transaction commits.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD@55154 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
