02-21-2014 07:22 PM
One of the reason we want to try this setup is so that the contained records will get destroyed before container, and when the last record is destroyed, we will destroy the container.
This setup seems to cause problems with the Event Triggers processor, especially when we do retention schedule recalculation.
Is it possible?
02-21-2014 09:02 PM
It's entirely possible and frequent. Though you can't destroy a document without taking it out of its container. So not sure what you mean by destroying the container when the last document gets destroyed. Why not just delete the container then?
Exactly what problem are you getting with the SET processing?
02-25-2014 12:56 PM - edited 02-25-2014 12:57 PM
Basically, I want to folder is the last item to get destroyed.
The jobs seem to be too complicated that the processor cannot even process them.
02-25-2014 01:19 PM
Ok, let me try to give you an example:
Say my schedule is "Destroy 5 years after Date Closed". I put it on both several document records and a folder. The folder contains all of the document records. My idea is I'm gonna put more documen records in that folder. Records have different Date Closed so they will get destroyed over times when the folder remains. The folder will be closed when the last contained record is closed, making the folder the last to be destroyed.
Does that make sense?
Right now none of the contained record have a Date Closed yet, and when the processor tries to calculate the retention schedule, it chokes.
02-25-2014 02:15 PM
Ok, with that example:
- What's the point of the schedule on the folder?
- Does the folder have a container?
- If so, what's the schedule on that container and does that container record type have "records of this type have no explicit schedule" enabled?
- When you save a document into the folder it will queue 2 SET's (one for the document and one for the container). the document SET is insignificant because there's no real logic to it (unless for some reason it itself is also a container). The container SET will check the trigger on the schedule and then check each contained item, ONLY if the trigger is based on a field which has a value or based on fields of contained items (like last action date of content). If the trigger is on date closed and there is no date closed, it exits because there's nothing to check (it hasn't been closed).
- 7.1 has some issues processing SETs. But how those impact this scenario depends on other configuration settings.
02-26-2014 10:30 AM
1. The schedule comes from classification. We are discussing about removing only the schedule from the containers.
2. In many situations, yes.
3. That could happen, but I don't think they wil cause problem.
4. Great info! Thanks! I'll test this.
5. Got it. I'm testing it with 7.3.3 to see if there is any issue there.