User Tools

Site Tools


pub:idocsapi

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
pub:idocsapi [2020/01/22 08:47] – [IFDUPSPLF] kkramerpub:idocsapi [2021/01/25 11:27] – [iDocs Programming API] kkramer
Line 3: Line 3:
  
  
-====== iDocs Programming API ======+====== iDocs Programming API'======
  
 iDocs has various methods to automatically print forms that are deposited in output queues.  There are two different types of form overlay engines which are the processors that automatically search defined output queues for spooled files to merge with form applications or form sets.  iDocs also provides api's that can be embedded into a job stream that executes the merge for defined print jobs.  The simplest is TFPRT which is intended to be embedded in the job stream following the program that produced the spool file to be processed.  With the more complex TRPRTAPI api, you can provide the necessary parameters to process any spool file on the system.    iDocs has various methods to automatically print forms that are deposited in output queues.  There are two different types of form overlay engines which are the processors that automatically search defined output queues for spooled files to merge with form applications or form sets.  iDocs also provides api's that can be embedded into a job stream that executes the merge for defined print jobs.  The simplest is TFPRT which is intended to be embedded in the job stream following the program that produced the spool file to be processed.  With the more complex TRPRTAPI api, you can provide the necessary parameters to process any spool file on the system.   
pub/idocsapi.txt · Last modified: 2023/07/25 13:08 by kkramer