Xperimental/rm 2812 public api test
A unit test to look for compatibility issues within the classes marked public API. The test will fail if it finds any exposed references to Alfresco non-public API classes from those marked as @AlfrescoPublicApi. The test searches within method signatures, fields, constructors, superclasses, inner classes and interfaces of public API classes.
See merge request !158
Feature/rm 3344 admin and guest
RM-3344 Ensure that admin can't lose clearance and guest can't gain any clearance.
Rather than use the guest role, as was used previously for classification clearance, we are
explicitly checking the username.
See merge request !160
This is a first pass at preventing changes to the clearance of admin or guest.
Previously we weren't allowing any changes to their clearance, but when
working with security markings, admin in particular needs to occasionally gain
a new mark when a custom group is created. Currently that clearing is not
happening, but this change does not prevent it, if needed.
Also remove an unused method from the CaveatMarkingServiceImpl, as the class
is already very full.
Xperimental/rm 2812 Mark Public APIs
First attempt to mark classes that should be part of the public API with \@AlfrescoPublicAPI.
I have also added a couple of \@deprecated annotations to classes where I thought it made sense, and
added comments to classes that I wanted to add to the public API but couldn't (due to their contract
being dependent on non-public API classes).
See merge request !138
Feature/rm 3144 patch for clearance level
Create a patch to migrate all users' clearance levels from the old classification model to
the new security marks model.
This merge request depends on getting !130 merged first.
See merge request !133
Having thought about this more, I don't think there's any problem adding
a deprecated class to the public API, as long as it's clearly marked as
such. It's deprecated at the moment because we think people might be using
it, but we want them to migrate to something else. Declaring this as part of
the public API formalises this process.
The RecordsManagementAuditService has the following dependencies:
RecordsManagementAuditQueryParameters <- RecordsManagementAuditService
RecordsManagementAuditEntry <- RecordsManagementAuditService
AuditEvent <- RecordsManagementAuditService
Feature 2.4/rm 3285
Added check not to be able to put null in cache, for nodes that are not records and don't have a filePlan.
Added unit test for it.
See merge request !128
Feature/rm 3284 ui tests are failing
This change addresses the failing builds both on master and on latest Aikau build plan. It also bumps up the Aikau version to 1.0.63 (further to @dwebster's confirmation this one is good to use).
See merge request !125
Feature 2.4/rm 3233 non electronic records can not have properties changed through rules in unfiled records
When setting a foreground rule to change one properties for files that enter to a folder from Unfiled Records, when trying to create a nonElectronic record sometimes because it was very hard to reproduce this issue, SetPropertyValueActionExecuter is executed before adding the Record aspect from RecordsManagementContainerType.onCreateChildAssociation() and that's why it fails when checking UpdateProperties capability.
When creating "rma:nonElectronicDocument" document formprocessor is used and at some point updateNode from node service is used to update the properties. Therefore I made sure that each time when udating "rma:nonElectronicDocument" node the Record aspect is added if not present.
See merge request !124
