Hello,
Recently, I installed Records Management Community 2.6.
I created a rule on my repository that, when renaming documents with a certain name, the documents are declared as archival documents.
These archival documents are then transferred from "Unclassified Archival Records" to another file.
As I think everyone, the beginning of conservation does not happen automatically, it must be started manually.
But when I try, I have this message that appears "Unable to initiate storage start. Contact your CIO":
It still bores me a lot because it's me, the CIO, if I may say so...
After several tests, I can see that when I remove my rule from "Renaming -> Statement archive documents", I can manually trigger the start of retention.
I absolutely want to keep this rule of renaming in order to facilitate the work of future users ...
What can I do?
I put my logs as attachments.
Thank you in advance,
Margaux
Hi Margaux,
I'm not sure exactly what's going wrong here. The log message suggests that the content is being declared as a record twice. Maybe your rule declares the document as a record, and then tries to move it to a record folder?
I tried to reproduce your scenario and everything seemed to work ok for me. I had the following:
When I upload a new document starting with "q" to my collaboration site folder then it is renamed, declared as a record, filed to the record folder and completed. This enables me to press the "cut off record" button to start the retention process.
I hope this is helpful, if not then please feel free to message me with more details of your problem.
Thanks!
Tom.
Is it possible to automate the 'cut off' of the records?
I can complete the record by the rule on the records folder under the rm site, but could not automate cut off.
I tried to setup the rule on the record folder and apply the rule which will perform 'complete event' action which is the part of the retention schedule to cutoff the record. But it does not work.
Just to update that 'Cut off' step is working well.
But the 'Destroy' step is not working when the time period is set as 'Immediately'.
Is this a bug in AGS?
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.