SignDoc Standard

This table contains information about potential issues that you may encounter while installing and using Tungsten SignDoc 3.4.0 and earlier versions. Workarounds are provided, when available.

ID	Title	Description	Workaround
2149193	Former brand name may still appear in application messages	The branding has been applied, but legacy references to the former brand name "Kofax" may still be present in certain links and application messages.
2110504	A signer can be created unexpectedly	When adding a new signer to a package and saving the changed package fails with an error, the new signer may still be created.	You can manually delete the created signer or keep the signer and try to solve the error when saving the changed package.
2095626	In the stage workflow newly added recipients get emails immediately	For a staged signing package in the PREPARED state, when a new signer is added from the Manage Client to a stage, the newly added signer receives an email even if the previous stage is not complete. However, the signer can use and start the signing session only when the previous stage is complete.
2068955	Copying a signing package fails when document locking is enabled	The process of copying a signing package fails when the document locking feature is enabled. Document locking makes the fields read-only after they are signed or filled, causing issues when these locked fields are copied into a new signing package, leading to an invalid state.
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 exceeds the number of allowed characters, the package cannot be created.	Provide a package name when creating a signing package.
1601384	TSP error message	When one of the signers doesn't have valid/proper attributes set for the TSP signature provider, an error message appears without indicating which recipient is causing the error.