pub:databasefields
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| pub:databasefields [2022/06/25 17:02] – created - external edit 127.0.0.1 | pub:databasefields [2026/03/10 18:51] (current) – kkramer | ||
|---|---|---|---|
| Line 25: | Line 25: | ||
| </ | </ | ||
| + | ====== Enhancement to convert PNG image to PCL and include into output PCL details (8.02 02/26/2026) ====== | ||
| + | 1. The process begans on the clients ERP system when a customer signs a credit card machine to capture the signature. Once the signature is captured, it will be saved to the predefined location on the IFS directory. | ||
| + | |||
| + | 2. The customer service representative completes the ERP invoice process, which will trigger 1.) The creation of the spool file, and 2.) Evoke the merge process of the spool file and the Invoice Form Application. | ||
| + | |||
| + | 3. The Merge Process can be evoked by the iDocs Engine (monitors an out queue to start the process) or by using the TFPRTAPI API. During the Merge Process, the Invoice Form Application will use the Mapped Field rules to extract the data from the spool file to use on the final document. During this process, we’ll need to trigger the captured signature image file to be pulled from the IFS directory (which we can pull from a static location or a dynamic location as long as the dynamic location appears on the spool file) and inserted in the documents based on a Mapped Field (Type 6). | ||
| + | |||
| + | 4. Once the Merge Process is complete, the output will be the PCL file which we will send to an out queue, and the originating spool file sent to an out queue for archive or secondary use. | ||
| + | |||
| + | 5. From this point, a distribution option can be chosen dynamically via RPG programming or based on predefined static configurations. | ||
| + | |||
| + | https:// | ||
| ---- | ---- | ||
| < | < | ||
pub/databasefields.1656201766.txt.gz · Last modified: 2022/06/25 17:02 by 127.0.0.1