 |
A transaction is the context for all document production activity. Transaction data (as XML) is often submitted on a request, in either ExpereTXN or VMP MISMO format, to provide the necessary inputs or content for producing documents. The ExpereAPI operations that utilize transaction data submitted on a request include the Generate, SelectAndGenerate, and Select operations.
A less common approach, also available in the ExpereAPI, is to submit a reference to a transaction. In this model, transactions are identified by system generated universal unique identifier (UUID). The UUID for a transaction is returned in the response when a transaction is requested; that UUID must then be used in subsequent API calls to select and generate documents. ExpereAPI operations that use this model include AutoSelect, AssembleDocument, and AssembleDocumentSet.
Using an UUID requires that the transaction data associated with the UUID (or referenced by it) is saved in the database for recall when the UUID is submitted. This method therefore can results in slower performance levels and also may introduce security concerns as the stored transaction data typically contains personal information about a borrower or other individual or entity.
|
