Versions Compared

Old Version 2

changes.mady.by.user Unknown User (gierlinger)

Saved on

compared with

New Version Current

changes.mady.by.user Manuel Gierlinger

Saved on

Key

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

...

Expand
titleAPI / Integration: Set a reading task, so that the signer has to confirm the reading
You can define a reading task, so that the signer has to confirm the reading of the envelope. Details about the configuration you find in the Reading Task Guide.


Expand
titleAPI / Integration: Can I store Meta data in the envelopes

Yes, you can store your own meta data in the envelopes.

Code Block
languagexml
themeEclipse
<envelope>
   <metaData>
      <element>custom data</element>
   </metaData>
</envelope>

The metaData element allows you to store additional, non-eSAW-data (e.g. for archiving) directly in the envelope. You can retrieve this information via getEnvelopeById call. An example of metaData is to store data for the archiving system in the envelope. The callback-integrating solution then can download the files (PDF & Audit-Trail) and store them directly in the archive.

...

Expand
titleIntegration: Custom callbacks on specific events
If you want to get a callback on specific events, e.g. when a signer rejects the agreement, you can use the following guide.


Expand
titleDocuments: How are PDF and PDF/A document types handled by eSignAnyWhere?
If you upload a PDF/A document to eSignAnyWhere it stays through the workflow a PDF/A valid document. If you are starting with a non-PDF/A document, the final document will be also a non-PDF/A document.

...