Item templates can apply alert message not appearing on template

[Elaine Hardy]

In the web client, item templates will sometimes apply an alert message not added at creation and not appearing on the template. This message can be either in the alert area or as a deposit amount. The alert is not visible in the web client and cannot be removed. It can be removed in the XUL client

Attempts to delete the alert message in the web client copy editor do not activate the save buttons, since no real action is taken.

For example, in the web client, an item can erroneously require a deposit, however the deposit flag is set to false and there is no amount in the deposit field. Checking the same item in the XUL client and the deposit flag might be set to true and a deposit amount is entered. This appears to occur when a specific template is applied, but the values are set correctly to not have a deposit in the item template.

When a copy alert message is triggered, there is no text in the message and no way to delete from the web client.

There does not seem to be a pattern that we ca discern for when an item template acquires the deposit or copy alert. Deleting and recreating the template will repair for awhile but the alert can come back.
Libraries have observed this with templates migrated from the XUL client and with templates created in the web client.

[Andrea Neiman (aneiman)]

Elaine or Lynn -- in which version(s) of EG do you see this bug?

[Elaine Hardy (ehardy)]

3.0.2 for me. We will be migrating to 3.2 this weekend

[Janet Schrader (jschrader)]

CWNARS also has this in 3.0.13. It is not in every template and doesn't happen every time or it would be more noticeable. Although, I have one cataloger that had it in every template that moved from xul to the web client and in several new templates created in the web client. That cataloger has deleted and made a new template for periodicals items 4 times. We wonder if there's a caching issue with that field.

[Andrea Neiman (aneiman)]

SCLENDS has signed a contract with Equinox to address this bug.

[Andrea Neiman (aneiman)]

We have been unable to reproduce this bug under testing in 3.2 and 3.3 (with the caveat that it is a hard one to test) - have any of the earlier reporters of this bug had it occur in 3.2 or later?

[Elaine Hardy (ehardy)]

With 3.8 we are seeing this issue again. However, we discovered that there is a "rogue" alert note in some templates that appears to have been suppressed in some versions of Evergreen. The notes are not in the proper format.

Rather than:

 "copy_alerts": [ {"note": "Shelved in Children's Workroom. Check out only to library staff.", "temp": "f","alert_type": 101}],

They are:

"copy_alerts": [], "alert_message": "3 DISCS",

or just:

"alert_message": "3 DISCS",

I suspect that they are from an error in template creation in an earlier version, perhaps in XUL. They may be an artifact left behind when an alert message was added in error to a template, and then deleted. Also, added and deleted prior to the newer alert system where you can set when the alert occurs.

If you either delete all instances of the rogue alert or delete the template and recreate it, the alert is no longer added to the item.

[Josh Stompro (u-launchpad-stompro-org)]

Bug 2022349 seems to be related to this issue.. except for the rouge deposit data mentioned, that may be a different issue.