Everyone attending the Hack-A-Way, please remember you can add discussion
topics and bugs you want to work on to the WIKI page here:
https://wiki.evergreen-ils.org/doku.php?id=hack-a-way:hack-a-way-2019-agenda
If you add a bug you want to work on you might find someone else who wants
to work
Hi Josh,
When we upgraded to 3.1 we were not ready to implement the web client. We
commented out the part of the 3.0.6-3.1.0 upgrade script that clears the
legacy copy alerts so XUL still had access to the copy alerts. We did
training on the web client on 3.1 but nobody did production
Josh,
This is probably un-helpful, but we let the upgrade script convert them
all to the new alert matrix feature and leave XUL in the dust. We
communicated this issue and fielded the questions as they came up.
Mostly: XUL is going away and this is "one of those things" that XUL is
losing. A
Hello, we are upgrading to 3.3 from an older version. And were planning on
a phased change over to using the web client after the upgrade.
I just noticed that the xul client cannot use the new item alerts, and all
existing item alerts are migrated from asset.copy to the new
asset.copy_alert
