SignDoc Standard

1782015: In case of an update, files remain in the repository and this leads to a replacement error when running the build_images.sh script.

Workaround: Unzip the .war file.

1. Open Dockerfile in the INSTALLDIR\docker\01_base_image\ directory.
2. Add -o option to the unzip command:

   # Unzip war files. This is required to be able to start up SignDoc on Linux.

   RUN unzip -q -o $CATALINA_HOME/webapps/cirrus*.war -d $CATALINA_HOME/webapps/cirrus/

3. Save Dockerfile.
4. Execute the build_images.sh script.

After successfully built, all Sample Docker images are ready to use.

1731040: The Administration Center Statistics page for the system with one account shows an empty list when selecting from the drop down list "Please select users".

Workaround: Log in as account administrator in the Manage Client and go to the Statistics page.

Fixed in SignDoc 3.1.0 Fix Pack 1.

1730716: File names of documents attached to the last email include character combinations consisting of a backslash followed by a letter or by a combination of digits when non-Latin symbols are used.

Fixed in SignDoc 3.1.0 Fix Pack 1.

1719215: A user with the Team manager role is unable to create a new team.

Workaround: An administrator can create the team, and then add the user with Team manager rights to edit the team.

1714282: The overlay image is displayed over the signature when the signature is removed. The image is temporarily displayed when the network connection is slow.

1693405: 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.

Workaround: 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: When one of the signers doesn't have valid/proper attributes set for the TSP signature provider, then a soft prompt error appears without any information about the recipient who is causing the error.

1466276: Disconnecting and reconnecting the database will stop periodic scheduled tasks.

Workaround: Restart periodic scheduled tasks after a database reconnection.

1348247: SignDoc does not support Asian languages for the localization of the tablet screen.

1267606: Some messages displayed in the Manage Client are only displayed in English or as an error id.