In the checkouts table shown on circulation and patron details the "Return claims" column should be wrapped in a conditional checking for the presence of a value in the ClaimReturnedLostValue system preference.
This bug might be dependent on Bug 24768? I'm confused by what's going on.
I thought it would be the easiest fix to add it to column configuration, because I wanted to be able to hide it for libraries not wanting to use it (it takes up quite a bit of space). Not sure if a conditional check would mean additional work is needed on not bug 24768.
Katrin, you also filed bug 25583, about how the Claims tab doesn't show if ClaimReturnedLostValue isn't set. If we make the return claims column also not show, does that resolve your issue in 25583? If both the column and the tab hid themselves when the syspref isn't set, then one wouldn't be able to generate a claim one was then unable to manage.
At the moment we're not using the Claims Returned feature because it doesn't work with our local policies. Our ClaimReturnedLostValue is not set but we still see the Claims tab on circulation and patron details. We agree that the tab should be hidden when the syspref isn't set because it is confusing to staff.
Never mind my previous comment. We discovered we had a blank space in the ClaimReturnedLostValue so that's why it was displaying. So nothing to see here.
But, following Barbara's comment, it might not be unreasonable to only show the Claims Returned controls if the syspref contains a *valid* lost value.
I don't recreate the original issue described in comment 0. (In reply to Andrew Fuerste-Henry from comment #6) > But, following Barbara's comment, it might not be unreasonable to only show > the Claims Returned controls if the syspref contains a *valid* lost value. I would suggest a check and warning on the about page instead. Should we update the bug report's title?
I believe this is still valid. I see the claims tab although ClaimReturnedLostValue is emty (and no blank space)
I believe the claims tab is now also used for the item bundle feature, so that might explain some change in behavior/might have taken into account.
This works if both BundleLostValue and ClaimReturnedLostValue are empty.