Release Notes for BankID Signing WYSIWYS¶

Noteworthy changes in BankID Signing WYSIWYS.

Only important bugfixes, API changes and new features are listed here.

WYSIWYS API Releases¶

Increased the allowed size of PDF documents in a PAdES sign order to 10 MB per document (Base64-encoded size).

Added content to the already existing signerInfo field in the PAdES-V1-API´s DELETE-call. It contains a JSON Web Token signer information if the data was requested during sign order creation.

Added new field signProperties.continueButtonTargetText to the PAdES-V1-API that will enable merchants to influence how the "Continue"-button on the finish-page is labelled. This way it will be possible to add a target to be displayed in the UI, e.g. by adding "MyMerchant´s Portal". Instead of "Continue" the button would be labelled "Continue to MyMerchant´s Portal".
Added new field signProperties.merchantWorkflowState to the PAdES-V1-API that allows WYSIWYS to differentiate between a stand-alone sign order and a merchant workflow. For stand-alone sign orders nothing will change. If a sign order is marked as part of a workflow, the WYSIWYS UI will show a notification on the finish page that will remind the user that others still have to sign and they should download the final documents from the merchant´s website when everyone has signed.
Slightly reduced the base-seal-size used for seal-position-validations to make defining a valid position easier. Note: The actual seal size remains unchanged.

Fixed HTTP-500 error when calling GET endpoints (e.g. /v1/signdoc/pades).
Corrected validation of seal position parameter to allow closer positioning on the Y-axis.

Make sure the app can handle big documents by only loading the first 15 pages and then lazy loading the rest of the document when the user scrolls down.

The warning message about attachments on a document have been toned down.
The continue button on the success page can only be clicked once to prevent multiple requests being sent.
Added an error_code parameter if it is present to the redirect URL when an error occurs during signing. This will allow merchants to handle errors better on their side.

Implementation of the new API fields mentioned above.
In case of errors during the signing process the same error code that is shown to the user in the front-end will be returned as parameter with the callback URL to the merchant.