Differences

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

--- pub:manualmerge [2020/09/22 14:22] – [Overview] kkramer
+++ pub:manualmerge [2022/06/16 11:55] – [Overview] kkramer
@@ Line 20: / Line 20: @@
 forms merge prior to printing. We can also archive and retrieve at a later time, or
 convert the print job to a *PDF form and other print file formats.
+The Manual Merge does have a limitation if the Multiple PDFs (of Bursting) in an  Email parameter under the iDocs Advanced Features F9 option is used.
+**Behavior to expect for the different settings of the Multiple PDFs (of Bursting) in an Email parameter:**
+When set to Y:
+  * The Form Application will only send out emails when merged and evoking the Smart Routing process.  This can be accomplished by selecting option 15. Merge with Spool File and then selecting  1. Merge/Print and using *FORMDEF as the destination out queue which will trigger the Form Application's Smart Routing configuration.
+  * Doing a manual merge with option 15. Merge with a Spool File and then option 11. **Merge/Email will not send out an email.**
+When set to N:
+  * The Form Application will work when evoking the Smart Routing process and doing a manual merge with option 11. to merge and email.
 **Manually Merge Form and Data**
@@ Line 58: / Line 69: @@
   * 4- Delete - Deletes the spooled file.
   * 5- Display - Displays the spooled file.
-  * 8- Convert to IFS - Runs ECVTSPLF archives the spooled file in the IFS.
+  * 8- Convert to IFS - Runs [[imailapis#ecvtsplf | ECVTSPLF]] converting a spool file to a specific format and subsequently saving the resulting format to a file within the IFS directory structure.
   * 9 - Attribute - Work with Spooled File Attributes.
   * 10- Email - Enables the existing spooled file to be emailed without merging the file with the form application.