Chapter 6. Evergreen 3.1.13
This release contains bug fixes improving on Evergreen 3.1.12.
All bug fixes refer to the web staff client unless otherwise specified.
-
Corrects a rounding error that caused fines to exceed the max fines
amount
(Bug #1704819)
-
Corrects an issue with printing Items Out receipts
(Bug #1790896)
-
SIP Visa payments are now recorded as credit card, rather than cash
payments
(Bug #1796942)
-
Converting change to patron credit no longer requires staff members
to refresh the screen to see the new credit
(Bug #1775639)
-
The patron summary now includes tooltips that were available in
the XUL client
(Bug #1772206)
-
The patron holds grid now includes a SMS Carrier column
(Bug #1748265)
-
When registering a new patron from Pending Patrons, the address
type dropdown now supports a default value
(Bug #1816180)
-
The Items Out grid now includes a Monograph Parts column
(Bug #1789257)
-
The annotate checkbox on the bill payment screen is now sticky
(Bug #1759343)
-
The holdings editor saves default values more consistently
(Bug #1812900)
-
Statistical categories and their entries are now alphabetized in the
holdings editor (Bugs
Bug #1744386 and
Bug #1777184)
-
The holdings editor now lists monograph parts in reverse alphabetical
order
(Bug #1760893)
-
Buckets created from the MARC Batch Import process are now available
in the MARC Batch Edit interface
(Bug #1440890)
-
The record bucket interface only displays the Merge action when
multiple records are selected
(Bug #1760599)
-
The menu in the top right corner is now named "Logout and more…"
(Bug #1796914)
-
Avoids Internal Server Errors on search result page
(Bug #1155706)
-
Double clicking the Place Hold button can no longer result in
multiple holds
(Bug #1029601)
-
Adds a more user-friendly interface for boolean filters
(Bug #1642337)
-
Improves consistency in terminology in the Local Administration
screen
(Bug #1776913)
-
Fixes an automated test related to translations and internationalization
(Bug #1768987)
-
Adds some foreign key functions that may be missing from your database
(Bug #1772028)