Versions Compared

Old Version 2

changes.mady.by.user Manuel Gierlinger

Saved on

compared with

New Version Current

changes.mady.by.user Christoph Bimminger

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Section

Example architecture diagram with call sequence

The diagram shows how a callback handler could push data to a document management system (DMS). Any other integration system that needs to process signed documents could be in place of the "Customer DMS" instead.

Architecture DiagramImage RemovedArchitecture DiagramImage Added


Section

Following steps describe the implementation in detail:


Number in the figureDescription
1eSignAnyWhere calls your CallbackHandler implementation when the envelope is finished (completed or cancelled).
2Your CallbackHandler stores the envelope ID in a persistent storage (disk, database) and replies with HTTP 200 on the HTTP request (1).
3A service implementation should permanently process the envelopes noted-down for processing.
4A service implementation will detect the noted-down envelope ID and process it as step by step queue processing.
(5)(removed)
6It should call the REST API call GET envelope/{envelopeId} to receive details about the envelope, including metaDataXml which was set by the DMS tagging application, and receive document IDs for the relevant documents.
7The documents, which are typically the signed PDFs, the Audit Trail PDFs, and in addition the legal documents (such as the CA22D certificate request form for disposable certificates) should be downloaded form eSignAnyWhere via API.
8After that, the application should upload the documents to the external DMS via the DMS API according to the requirements of the DMS; and use the tagging retrieved from the metadata.


Once completed, the callback handler implementation (i.e. the asynchronous service) should delete the envelope from eSignAnyWhere when it is not used in eSignAnyWhere any longer and after the document, the audit trail and other legal evidence documents have been successfully transferred to a permanent storage outside eSignAnyWhere.

Alternatively, a data retention job can be configured on the organization to perform an automatic cleanup. But note that the retention job would not identify/stop when the transfer to the permanent storage failed.


...