10,729
edits
Important: Deprecating old WebView — Publish failed error
Storage analyzer: Difference between revisions
Jump to navigation
Jump to search
→DocuSign report
| Line 265: | Line 265: | ||
== DocuSign report == | == DocuSign report == | ||
This report makes sense if you use electronic signatures from [[DocuSign]]. It lists technical details about the documents waiting to be signed. | |||
This kind of information can be useful for Resco support when investigating problems. | |||
<syntaxhighlight lang="text"> | |||
Sign jobs: | |||
SignPending (LocalId: 3b5bf584-2b1d-45e3-a15e-7e71267532db) for [annotation, Signature.png] -> [resco_questionnaire, Q2 Approval] | |||
DownloadPending (ServerId: 8da6a51f-f1e9-420d-a4ed-fb06b72cddb6) for SharePoint doc img_210312_103233.jpg -> [opportunity, Standort #2] | |||
</syntaxhighlight> | |||
=== Explanation === | |||
Document signing is a complex process consisting of several steps: | |||
* Document is uploaded to the signing server. | |||
* Document is signed by the server. | |||
* Signed document is downloaded to the client, where it replaces the original document. | |||
In the above example: | |||
* Signature.png stored in an annotation record attached to a questionnaire: Signing process initiated. | |||
* Snapshot attached to an opportunity record: Signed file waiting on the server for download. | |||
== Database internals report == | == Database internals report == | ||