Release 23.R3.1 (11.52.1)

Bug Fixes

Accessibility

• PB-97462: Fixed the following issue. The signatures applied to a document in an accessible transaction were invalid if: (1) the Sender added to each Signature Field a Signing Date autofield; (2) the Signature Fields were signed in an order that differed from the order in which these fields had been added to the document.

• PB-97438: Fixed the following issue. An accessible transaction had two signers, and each Signature Field was assigned one Signing Date autofield. Each applied signature should have carried information about the fields locked to it, but this information was either missing or incomplete.

• PB-97203: Fixed the following issue that occurred in an accessible transaction. In a signed document, where a single Signing Date autofield should have appeared, two Signing Date autofields appeared. Moreover, these autofields overlapped.

• PB-97905: Fixed the following issue. A user downloaded a signed document that was part of an accessible transaction that had two signers, two signatures, and a Signing Date autofield for each signature. The downloaded document wrongly indicated that two Form Fields had undergone "Property Changes".

Printing

• PB-96480: Fixed a printing issue that was caused by a missing XObject.

Upcoming Changes

• PB-93756: Starting in Release 23.R5 (11.54), the format of all Date fields in exported CSV files will be "yyyy-MM-dd HH:mm:ss". This applies to the following CSV files: (1) Notary Journal Export; (2) Transaction Usage Report; (3) Transactions Scheduled Report; (4) Account Scheduled Report.