v9.1
Bug# 5852

This seems to be a new issues introduced in ILLiad 8.7 when we switched to Delphi XE 8. To reproduce, submit an OpenURL request using the included URL both with and without a session. When you're already logged in, the cyrillic characters are rendered correctly in the author field and a ligature is used in the title. If you don't have an active session and are sent through the logon2 page, those fields will be rendered as ?s or boxes, indicating a problem with the form state encoding. I confirmed this URL worked correctly on ILLiad 8.6.x and earlier.

For OpenURL requests, if the patron already has an active websession and do not have to log in the characters are correctly translated.

The alignment for the buttons at the bottom of ChangeUserInformationare set to be right-aligned by default. For consistency, these need to be left-aligned like in the NewRegistration page.

Bug# 7683

v9.1
Bug# 7323

Remote auth validation does not load the user's reported session id, duplicate form submissions aren't being prevented.

Bug# 9013

The date shows up correctly in the client and the database but not in the transaction notes.

v9.1
Bug# 7847

When adding carriage returns, it breaks the JSON parse.

Workaround: Use a <br> tag before starting a new line to ensure the alert will display properly.

v9.1
Bug# 7172

The web pages with extra div tags include:

EditArticleRequest
EditBookChapterRequest
EditConferencePaperRequest
EditGenericRequestTesting

Bug# 6022

Web alerts for Status and DeliveryLocation don't appear on the web pages for users to when generated through the use of the AJAX (https://support.atlas-sys.com/hc/en-us/articles/360039292194-Performing-an-AJAX-Request-to-View-Customize-Web-Alerts).

Workaround: Adding the <#ALERTS> tag will show all of the alerts (see attached image)

v9.1
Bug# 5893

In an ILLiad addon:

When you make changes to transaction fields, route the transaction and then SaveDataSource it will undo the Route action.

Workaround: This can be avoided by saving before routing.

Bug# 4681

The ILLiad web DLL will perform special handling for text values equivalent to 'null,' replacing them with an actual null value when it updates the database.

Bug# 4602

ILLiad does a case-insensitive comparison of the field value and will treat a user record with the LastName of Null as null when it updates the database.

Bug# 4601

The renewal button doesn't consider the due date and the RenewalWindowDays/RenewalBeforeWindowDays customization keys when determining if the button is visible in the web pages.

Bug# 4571

The lending web pages prevent the display of the billing information table when BillingActive is set to false.

Workaround: If BillingActive is set to BillingActiveLending, then the BillingInformation table will always display in the lending web pages.

Bug#4444

When a user changes a Lender's password from the ILLiad client, it only changes the password for the NVTGC that the user is logged into the client under, instead of changing it for all NVTGCs. As a result, the lender may be able to log into the client under that particular NVTGC but unable to log into the web.

v9.0 & 8.7
Bug# 4436

The invalid username status line doesn't seem to be triggering the SLLoginFailed customization key on the Forgot Password page. The status line does appear if triggered on the logon pages.

v9.0 & 8.7
Bug#4147

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

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.