1668896: When the document is zoomed out the default size check boxes or text fields are no longer lost under the guide me cursor.

1660124: In case an invalid access code is entered the existing authentication token is now added to the refresh token request and no unexpected authentication error occurs anymore.

1651486: When storing the document name containing Japanese characters in the database, these characters are not replaced any more with "?".

1650340: When a signer was replaced in a signing package the server returned a signer order error after the signing package was updated.

1644637: For the LDAP user, the last signed in value was not updated in the Manage User overview.

1644635: Log files were not deleted per the rolling size.

1641436: The Wacom STU signature capture failed when the signature field was placed in a corner.

1641371: In a document with more than one page, the field masks appeared on every page and not only on the page where the field was defined.

1634665: An internal error occurred when the browser was refreshed on the Finish or Goodbye page of the Signing Client. The Application Loader page was displayed unexpectedly. Another refresh took the signer to the Welcome page.

1633782: When using the masking for check boxes, the values were not fully covered.

1633287: PDF documents that contained scanned data on the first page (such as a photograph) exceeded the allowed limit for thumbnail images.

1631874: The place holder for the access code was not replaced in the SMS for French.

1629244: The message "Resource not yet available" is replaced with "Duplicate field name:", adding the value of the field name.

1626287: In-person signing on an iOS device was not possible when the browser pop-up blocker was enabled.

1624035: The cover page of the final document did not contain direct links to the signed documents and audit trails.

1623859: It was possible to select "copy value" for empty configuration values.

1622754: The status view for SMTP configuration showed a "connection error" message whenever the configured SMTP account required a password.

1622474: Sometimes the content of the mail settings overlapped with other settings.

1620714: Settings for the log file were not applied to the configuration.

1619618: The field "Document Description" was used as file name for a template package.

1611083: Starting an in-person signing session where the signer was assigned to a stage and an individual signing field lead to an error message.

1610781: The sidebar for the Package wizard in the Manage Client closed unexpectedly. The sidebar was closed when clicking in the sidebar and releasing the mouse outside the sidebar (drag and drop).

1609708: If a large document was signed using a Swedish BankID, a message indicated that the process could not be initiated.

1602826: The BankID order reference ID was not included in the audit trail of the final document.

1597252: The layout in portrait and landscape modes for mobile devices did not ensure selection of the "TSP signature" when all signing methods were available.

1586125: The SignDoc Standard service didn’t get installed when the JDBC.password contained an ampersand character (&).

1582170, 1581991: As soon as the Authentication Method was set to "Code," the following text was added to the email message in English: "You will need to enter an access code to open the document(s). It will be sent to you by SMS when you start the signing session." Translation to other languages and text editing were both unavailable.

1575863: No softprompt error was shown for the wrong password when generating an API Key.

1564894: Creating the remote URL for a signer differed when using "Send e-mail" or creating the URL via the REST API.

1558362: The consent step was displayed on the Welcome page although consent options were turned off for the signer. The consent step was hidden correctly once the signer clicked the NEXT button.

1558174: After a signing package was created, the customer called "Get a remote session signing URL for the specified signer" REST API method to retrieve the signing URL of the signer. When the signer was redirected to the Signing URL, the signer received a "The signer token is invalid" error.

1553886: A Signing Package using a SignDoc Template wasn't created in SignDoc when Kofax TotalAgility updated a document that did not have a "src_id" or "signature_field" information in the request.

1546000: The "Start in-person signing" dialog page didn't highlight "Select all".

1544421, 1542993: When a document was created with optional interactive fields and when filling an optional interactive field such as a check box, signature field or text field as a recipient, then the cursor didn't move to the next required field.

1540367: The REST API request "Prepare Signing Session" with signtype = common (for in-person signing) only worked if the API Request "Schedule a signing package" was executed in advance.

1530552: There was no warning message in the Manage Client GUI to inform the user about an expired S/MIME certificate.

1499901: Capturing a photo in iPhone portrait mode caused the image to be rotated in the document.

1497648: Due to a complex LDAP search filter in service_configuration.properties, the SignDoc service was not able to start.

1497512: When the SSO user was suspended and attempted to log in, that user was left on the SignDoc login page without any information.

1448417: The signers' color scheme was different than expected when a signing package was prepared and signed.

1448002: When using the Mozilla Firefox browser, each user entry had an additional background color.

1438942: When signing packages were created from Kofax TotalAgility, the color was missing for recipients.

1411721: In Google Chrome and Mozilla Firefox, uploading a document didn't work. Uploading worked as expected in Internet Explorer and Microsoft Edge.

1375030, 1375029, 1375028: The SignDoc activity was suspended when the document template had more than one text box or check box. An error also occurred when a document variable was not present when the document provided in the template was used.

1347831, 1267473: The confirmation email after the reset of a password didn't contain information about the account.

1306004: The Resolution in dpi for converting field coordinates to document coordinates could not be expressed as a negative number.

1272913: When using iOS, the downloaded version of both e-sign consent and data protect privacy consent contained corrupted non-ASCII characters.

1267512: After returning to a completed, required text field, the guided form filling pointer didn't move to the next required field.

1267464: The camera view was rotated 90 degrees counter-clockwise in Microsoft Edge while signing.

1225638: After iPad rotation, the signing package layout was broken in the document editor and it was restored later.

1167914: Sometimes the color scheme for recipients was inconsistent within the same signing session.

1117886: The softprompt message indicated a successful upload at the time when the format data showed "Not supported".