Bug#3583

When printing the PrintAddress.doc template from the client, the PrintAddress.xlsx data source file that is created has the Legacy style headers for both the Legacy queue and the Print queue.

v8.7.2
Bug#3797

On the bottom status bar of the Staff Manager, some messages are showing up multiple times. See the attached example.

Bug#3826

The data source for the Billing Manager printing process still defaults to C:\illiad\print\ in the Customization Manager, but newer installations of the ILLiad client don't create this folder. This only occurs for new installations who don't have the print folder from previous installations.

v9.0 & 8.7
Bug#3887

Outgoing Notifications grid columns reset their size whenever Outgoing Notifications is closed or the client is restarted. v9.0

When you export the report in Excel, everything is left blank except for the parameters. v9.0.3 and web report v9.0.0

Workaround: The same web report data can be extracted from ILLiad using an ODBC link. See https://support.atlas-sys.com/hc/en-us/articles/360011809414-Administrative-Web-Reports for examples of queries that can be run to obtain this information.

When the lending library imports the lending request, it puts the LenderAddresses.DefaultShippingMethodLoan value into the Transactions.ShippingOptions field instead of using the LenderAddresses.DefaultShippingMethodArticle value. v9.0.3 & 8.7.3

Requests submitted through the ILLiad API are not using the database defaults set in the Customization Manager. For example, a request will not appear on the ILLiad reports even though they appear in the client if the CopyrightAlreadyPaid key is set to Null via the API since the reports are looking for the default value of No or Yes. v8.7.4

Workaround: Add the No field to requests submitted through the API.

If a system addon is created but FormNames are also entered, the addon will be loaded for both the system script environment and for each form script environment that is specified. An example where this causes errors is when registering system event handlers which can only be registered to a single addon.
 
Forms are not relevent in Library, System, or Server addons.

In the Customization Manager, edit an existing Z39.50 server or create a new one. Modify the ISSN Search field. When you save your changes, the ISSN Search field will remain yellow. v8.6

Error sending request popup will appear stating "Could not execute JDBC batch update".

Bug# 1453

FormLenderAddresses will throw an exception when the request tab is opened without the lender being saved first.

Bug# 1560

The Force Password Reset checkbox does not have the focus prior to the Ok button for proper Top->Bottom & Left->Right expectations. v9.0.3

Some customers are experiencing issues with the 3 of 9 barcode font being removed during the 9.0 client update. This seems to be dependent on previous install/update scenarios.

Workaround: The issue can be resolved by manually installing the font or re-running the client installer in repair mode.

Repro Steps
The YazLoader class (only used for loading Z39.50 in an addon) has a typo and should be libraryname. Also the YazLoader is not loading the zlib1.dll file despite the log indicating it has. It actually loads libxslt.dll a second time. zlib1.dll is a dependency of libxml2.dll and not a direct dependency of yaz3.dll which has allowed it to not work with bundling the zlib1.dll with addons using this. Currently the LendingAvailabilityAddon for Wisconsin is the only user of this code.

[DllImport("kernel32", CharSet = CharSet.Unicode, SetLastError = true)]
private extern static IntPtr LoadLibrary(string librayName);
....
log.Debug("Loading zlib1.dll");
LoadLibrary(System.IO.Path.Combine(path, "libxslt.dll"));

Repro Steps
ILLiad reports sometimes generate with more sites than were intended.

Steps to Reproduce

1. Find or set up an ILLiad server that has multiple sites
2. Go to <illiad_server>/ILLiad/webreports
3. Choose any report and select one of the sites that is not "ALL". Make sure that the selected site is the only site that is selected.
4. Generate the report, notice that the

Workaround

If you use the menu links when navigating the WebReports module, this issues does not occur.

It is very confusing to fail validation while using a screen reader because it isn't apparent that validation failed.

It should likely alert the user on page reload.