Steve, I think your comment from 2013-03-27 is accurate. I think the best solution would be a definable 'expiration period' on the event definitions themselves. After an event expires, the target is again eligible for consideration. In addition to this new field, implementation would likely just be a filter on the JOIN which brings in the existing events.
Does anyone else with more A/T experience see a simpler way out of this problem?
Steve, I think your comment from 2013-03-27 is accurate. I think the best solution would be a definable 'expiration period' on the event definitions themselves. After an event expires, the target is again eligible for consideration. In addition to this new field, implementation would likely just be a filter on the JOIN which brings in the existing events.
Does anyone else with more A/T experience see a simpler way out of this problem?