SignDoc Standard
This table contains information about potential issues that you may encounter while installing and using Kofax SignDoc 3.3.0 and earlier versions. Workarounds are provided, when available.
| ID | Title | Description | Workaround |
|---|---|---|---|
| 1962069 | Issue with displaying the header in the document signing view | When a signer opens a document for signing, the header with the Done button may not be displayed, even though the user can fill and sign the document. | To leave the signing view, either click the browser's Back button or refresh the browser to display the signing header. |
| 1961929 | Issue with custom locale containing country code | The custom locales feature for preferred signer language does not work for locales with country codes other than BR and CN. | Use locales without the country code. |
| 1960912 | The Save button triggers a message instead of exiting the view | When changing the stage of a recipient after starting the signing package, the Save button may not automatically exit the view after applying the changes. Instead, an alert appears with the message "You have unsaved changes." | Click the Save button again to exit the view. |
| 1959835 | No new signing notification for an updated signer | The updated signer doesn't receive the new signing request email. | Use the send email option to send the email manually. |
| 1836491 | Exceeding the allowed number of characters for the package name results in an error | The default package name is derived from the user's name. Therefore, if the final package name contains more than the allowed characters, the package cannot be created. | Specify a package name when you create a signing package. |
| 1714282 | Issue with overlay image | The overlay image is displayed over the signature when the signature field is removed. The image is temporarily displayed when the network connection is slow. | |
| 1693405 | Issue with values less than one for the order of the signer |
For previously created packages in the Prepared state including a value for the order of signers less than one, the scheduling will fail with cirrus.constraint.violation. Exception after migration from installations prior to SignDoc Standard 3.0 FP2. |
Use Get all signers for the failing packages or use Get packages for signers where values for the order of signers is less than one. Then use the appropriate PUT functionality to update the order for the signers by incrementing the value by +1 starting at 1. If the order of signers is completely misplaced (missed orders in the sequence) and is not correct as per the sequential processing, the PUT functionality can be used to give new signer orders starting from 1 incrementally for each signer to the package. |
| 1601384 | TSP error message | When one of the signers doesn't have valid/proper attributes set for the TSP signature provider, then an error message appears without indicating which recipient is causing the error. | |
| 1348247 | Tablet screen localization | SignDoc does not support Asian languages for the localization of the tablet screen. |