Web Client: Target All Statuses

[Scott Thomas]

We are at 3.1.6. In Check In, when you select Target All Statuses as a Checkin Modifier, it does not appear in the red bar near the top of the screen. I am not sure if this means it is or isn't actually working. It remains checked in the dropdown selections under Checkin Modifier.

[Kathy Lussier (klussier)]

Hi Scott!

I've always found this particular check in modifier confusing. It needs to be used in conjunction with the Retarget Local Holds modifier. Basically, Retarget Local Holds is needed at a minimum to perform retargeting of local holds. You add the All Statuses modifier if you want to retarget statuses beyond In Process. This addition captures checkins for Missing, Lost and other problematic statuses.

If you have both modifiers enabled, you'll see that the language in the red bar changes.

Having said that, I found a problem where the retargeting did not immediately occur when checking in an item that would cause an alert to pop up. Even if the system is configured to suppress that alert, the copy didn't immediately retarget. I needed to check in a second time with that check in modifier enabled to get the regargeting to work as expected. I think this would be a separate bug.

[Michele Morgan (mmorgan)]

Kathy,

Could your item initially have been in a non-holdable status? I found the retargeting to occur as I would expect with both "Retarget..." checkin modifiers turned on. Only one checkin was required with those modifiers to get an existing hold for a newly added item in "In process" status to capture.

This was true whether or not the item had an alert.

I'm testing on 3.1.7.

[Kathy Lussier (klussier)]

OK, thanks for following up Michele! My comment was based on a misunderstanding of how this feature works.

In that case, I would say the web client's use of this check in modifier works the same as the xul client. I'll set the bug to Invalid, but, if I missed something Scott, add a comment and set it back to new.

[Scott Thomas (scott-thomas-9)]

Hi Kathy,
   I appreciate the explanation and what you said makes sense. Having said that, it still would be nice, for the sake of consistency, if Retarget All Statuses could also appear in the red bar.

Thank you,
Scott

[Scott Thomas (scott-thomas-9)]

Oh I see what you mean. If you have both checked, it adds the word "Always" to the message in the red bar. Maybe we just need a minor wording change in both the Modifier selector and the message: Retarget Local Holds (Inprocess) and Retarget Local Holds (All Statuses). How does this sound?

Scott

[Kathy Lussier (klussier)]

I've removed the Invalid status while you all discuss best approaches. In my mind, the confusing aspect isn't necessarily which statuses are retargeted, but the fact that both need to be checked for Retarget All to work.

[Michele Morgan (mmorgan)]

I wonder if it would make sense (or be possible) to automatically check the "Retarget Local Holds" modifier when "Retarget All Statuses" is checked since they must both be ON for "Retarget All Statuses" to work.

[Lindsay Stratton (lstratton)]

It would really make sense that "Retarget Local Holds" and "Retarget All Statuses" were combined into one, since they effectively serve the same purpose.

That "Retarget Local Holds" ONLY works with "in process" status items is kind of ridiculous. Not all newly added item records have the status "in process", and retargeting holds is very important for items that have been marked damaged, missing, etc.

[Terran McCanna (tmccanna)]

+1 to either comment 7 or 8