9,310
edits
Synchronization steps: Difference between revisions
Jump to navigation
Jump to search
→DocuSign offline signatures
| Line 790: | Line 790: | ||
=== DocuSign offline signatures === | === DocuSign offline signatures === | ||
If you enable true-offline legally-binding document signing using a third-party tool by [[DocuSign integration|DocuSign]], the signed documents are submitted to the server during synchronization | If you enable true-offline legally-binding document signing using a third-party tool by [[DocuSign integration|DocuSign]], the signed documents are submitted to the server during synchronization. | ||
<syntaxhighlight lang="xml"><DocuSign Signed='1' TotalTime=' | Signing runs at the start of the sync. Documents are signed one by one in a loop, while the user sees a progress bar. If there is no problem, signed documents are stored in the client database; from there they will be uploaded to the server in the sync upload phase. | ||
Signing summary: | |||
<syntaxhighlight lang="xml"> | |||
<DocuSign Signed='3' Failed=’1’ Waiting='1' TotalTime='5245ms'/> | |||
</syntaxhighlight> | |||
Should the signing encounter a signing error, it is presented in the log in the following way: | |||
<syntaxhighlight lang="xml"> | |||
<ERROR>DocuSign failure: … </ERROR> | |||
</syntaxhighlight> | |||
Any DocuSign error breaks the signing loop. However, the error is considered non-fatal (i.e., a warning) and the sync continues. | |||
What happens to the document? | |||
* An unsigned document is uploaded to the Server. | |||
* On the client side, the document is still marked as changed and the signing will be reattempted on the next sync. | |||
== Closing remarks == | == Closing remarks == | ||