You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have made an update from version 2.4.456 to version 2.15.349. Everything seemed to work! After some further tests I had to find out that something has changed.
In version 2.4.456 it was possible (with some effort) to distinguish between signed and unsigned signature fields. So after calling the method getAnnotations() the fieldValue was filled with "Sig" for fieldType="Sig". So that was for me the distinction that a signature field was already signed. In case of unsigned signature fields the fieldValue remained null.
In version 2.15.349 the fieldValue in the resolved promise is always null. Also in case of already signed fields. See following:
A verfication of a digital signature is not important for me. I only want the fieldValue to be filled when an annotation of a type "Sig" is filled.
Is it possible to implement this????
Or is there already a way distinguish between signed and unsigned signature types????
The text was updated successfully, but these errors were encountered:
I have made an update from version 2.4.456 to version 2.15.349. Everything seemed to work! After some further tests I had to find out that something has changed.
In version 2.4.456 it was possible (with some effort) to distinguish between signed and unsigned signature fields. So after calling the method getAnnotations() the fieldValue was filled with "Sig" for fieldType="Sig". So that was for me the distinction that a signature field was already signed. In case of unsigned signature fields the fieldValue remained null.
In version 2.15.349 the fieldValue in the resolved promise is always null. Also in case of already signed fields. See following:
A verfication of a digital signature is not important for me. I only want the fieldValue to be filled when an annotation of a type "Sig" is filled.
Is it possible to implement this????
Or is there already a way distinguish between signed and unsigned signature types????
The text was updated successfully, but these errors were encountered: