Hi Dave,

Thanks for your response. I'm a little confused about your distinction between available and requestable. The "requestability rules" screen always refers to marking vials available/unavailable. The only exception is the administrator override option using the "requestable" column, which we don't use.

In any case, we now have 13.2 installed on our development server, and I did some messing around. First, I should explain that my query is looking to find "the first x available vials" for a list of subjects and mark them unavailable. Which means that the results will change depending on what other rules are run before the query, and it may return a different number of vials as well.

So, with no other requestability rules being enforced, my query returns 798 vials, the import says that 798 vials were marked unavailable based on that rule, and SpecimenDetail shows 798 vials unavailable with my query as the reason. Perfect.

Then I added the Locked in Request Check to the requestability rules, after my query. The query and the import still say 798 vials, but the number of vials in SpecimenDetail is 718. I suspect that most of that is legitimate - the vials were re-marked as unavailable due to being locked in a request. However, the 6 vials I mentioned originally are now available. It seems that the "Locked in Request Check" is remarking them as available, which it really shouldn't be doing.

Finally, I moved the Locked in Request Check BEFORE my query. I couldn't do this in 13.1, but it's allowed in 13.2. It works perfectly again. We hope to upgrade our production server soon, so I can work around my problem by re-ordering the rules.

I looked at the "affected vials" for the Locked in Request Check rule and the 6 vials I'm having such trouble with are definitely not in there, so I just don't understand why they would be affected by the Locked in Request Check rule at all.

- Jen