SigningHub v7.7.8.16
December 2020
- Client Side Signing fails (using tokens) when two recipients performs signature simultaneously
- Two recipients can perform signature simultaneously using client held keys (tokens)
- Workflow finish process fails while using iPAD or iPhone
- Workflow can be finished seamlessly while using iPhone or iPAD
- Document Size increased due to miscalculations while computing dictionary size
- Document size doesn't increase while computing dictionary size for PAdES Part 2 or PAdES Part 4 signatures
- Document couldn't receive due to an error in push notification
- Document now received and processed while using mobile devices, even a push notification fails to receive
- Only Me workflow type didn't support multiple occurrences for document owner while perform client side signing
- On perform client side signing in case of only me workflow, the document owner can process the workflow even when he is added twice in the workflow
- Signature Statistics under enterprise settings fails to respond due to lack of performance
- Database query to fetch signature statistics records for enterprise has been improved for better performance
- Signature and Document Statistics was missing an export option once view stats through provided hyperlink in SigningHub Admin
- Signature and Document statistics can now be exported as an Excel document, while viewing stats using enterprise hyperlink
- Single public authentication profile fails to auto trigger when only a third party authentication configured
- Public authentication profile (other than password based authentication), when configured as the only available public authentication profile, now auto triggers upon browsing SigningHub application
- SigningHub admin connectors list shows null values under listing while loading list
- Connectors list shows language keys values and proper labels while loading the list of connectors in SigningHub admin
- User invitation was unsuccessful due to case sensitivity in email address
- User invitations were unsuccessful and didn't proceed in case user email contains any letter in CAPS. This has now been validated and user email address is no more case sensitive
- Document upload failure for specific documents
- Document uploading execution refactored to bypass the validation if there are no attachments added for the document being uploaded. This was causing an issue while uploading even for a document without any attachment.