Signer Component v1.1.7

New

• documentCompleted added as a failureReason value on signingFail — fired when the document was already signed in another browser or device (server returns completed or recipient_state). The component shows an informational message to the recipient rather than an error state.
• signingFail now fires for document state changes detected after load:
  • rejected — fired when documentObject.is_rejected is true
  • documentExpired — fired when documentObject.state === 'expired' or the expires date is in the past
  • cancelled — fired when documentObject.state === 'cancelled'
  • deleted — fired when documentObject.is_deleted is true
• signingFail document load errors now correctly mapped — 401/403 fires sessionExpired, 404 fires removed, all other errors fire signingError

Updates

• Field save debounce increased to 1500ms — reduces unnecessary save requests on fast or repeated input
• saveField reliability improvements
• Signing interface positioning improvements for better layout across different container sizes. Existing customers may require a signing version upgrade to benefit from this change — contact support.