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
Feature 2.4/rm 2925 no option to delete destroyed record folder
RM-2925 - No option to delete destroyed record folder (which maintain record metadata after destroy)
Made Delete action available for destroyed record folder, added unit test class.
See merge request !92
Feature 2.4/rm 3283 outlook integration email with attachments
RM-3283 - Outlook Integration:Emails cannot be added to Unfiled Records (having a rule set) using Alfresco Outlook Integration
When adding emails with attachments in alfresco a hidden folder of type wpsmail-v2:attachment-folder (subtype of cm:folder) is added to hold the attachment files. When such an email is added in Unfilled Records container the RecordsManagementContainerType.onCreateChildAssociation policy is fired which transforms any subtype of folder into a record folder. When the rule tries to file this folder in another record folder we get an exception from trying to add a record folder in another record folder.
To fix this issue I added an extra check to avoid applying the conversion rule on hidden nodes. I also added a unit test for both hidden and non hidden folders.
See merge request !123
Feature 2.4/rm 3216 regression imap
RM-3274 - Error creating bean with name 'imapServiceBootstrap'
I added an invalid authentication util bean reference to the extended IMAP service and the setter was missing.
See merge request !117
Hotfix/rm 3114 patch fails
- Update release version to 2.2.1.5
- make admin service a listener, ordered to execute last
- protect service behaviours from execution until custom map is loaded
- integration tests
@abozianu and @onechiforescu please take a look at this too.
See merge request !86
Feature 2.4/rm 3030 preview not available declared record
RM-3030 - The documents declared as records in their Details page don't have the preview available afterwards.
I've noticed different behavior when doing steps in different order: if the file is declared as record before navigating to document details page, the error doesn't reproduce; if document details page is accessed first and after declare the file as record, there is an Access Denied exception.
In the first case the node for preview has the File Plan aspect, in the second one it doesn't.
See merge request !105
Feature 2.4/rm 3266 foreground reject action in unfiled records not working
RM-3266 - Documents get into a "hybrid" state when the Unfiled records inherited from File Plan rule rejects declared records.
If we run the reject rule in foreground it will run in the same transaction with create-record. **CreateRecordAction** will move the file to RM site and add all the RM aspects to it (including rma:filePlanComponent) then **RejectAction** will move the file back to the collaboration site and remove all the RM aspects from it. Because the two actions run in the same transaction **FilePlanComponentAspect.onAddAspect** will run at the end of the transaction to set the property rma:rootNodeRef and apply the rma:filePlanComponent aspect on all the renditions. By setting the property rma:rootNodeRef the **rma:filePlanComponent** is added back on the node.
When listing the files in the community site these nodes match the rmDocLibRecord template becuse they have **rma:filePlanComponent** aspect but we fail to list them because they are not records. The rejected files should match rmDocLibRejectedRecord template.
I added an extra check in the onAddAspect method to make sure we don't add back RM properties if the aspect rma:filePlanComponent has been removed in the same transaction it has been added.
Another solution that worked is changing the notification frequency of the onAddAspect method from **NotificationFrequency.TRANSACTION_COMMIT** to **NotificationFrequency.EVERY_EVENT** but I think it will affect the performance a lot more.
See merge request !113
