Differences

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

--- pub:smartrouting6 [2018/05/24 16:06] – external edit 127.0.0.1
+++ pub:smartrouting6 [2020/10/23 13:21] – kkramer
@@ Line 76: / Line 76: @@
 **Invalid Out Queue** : if target destination is unresolved, the output is removed or moved to Invalid Out Queue (if specified)
+An enhancement for IFDClient was added in 6.95 (7/24/20). If the IFDClient DataQ is specified, when smart routing is processed, it will create a temporary PDF into /tmp/idocs – this PDF is independent with any PDF created for SR mail, then a message is sent to data queue. If IFDClient is running, it will be able to download this PDF into PC user.
+By default, Data is *SPJUSR which is the user ID of original spool file. Thus, if IFDClient is monitoring the data queue with key is user ID, the PDF will be sent to respective user ID.
 ==== Email Settings ====
@@ Line 105: / Line 107: @@
 ==== Print Settings ====
 Print Settings is also defined as Email Settings
+===== Smart  Routing Examples =====
+==== Example 1 ====
+Description:
+We’ll use the EXAMPLE01 Form Application with the Invoice spool file which is a one page invoice.
+When the Form Application is merged with the spool file sequences 1, 2, and 3 will be outputted to a Destination Out Queue with a writer for printing. In our example the Out Queue is called GOODOUTPUT.
+Sequence 4 has a Destination Out Queue *EMAILPDF which is a reserved destination. *EMAILPDF will trigger iDocs to use Smart Routing. In our example we are using the iMail Address Book (option 3. Work with Users from the iMail menu) to acquire the email destination address; and we are using option 14.Smart Routing on the Form Application to configure the settings to trigger the look up of the email address by using the User Profile of the spool file owner.
+In our example when Smart Routing is triggered the configuration will use the User Profile (*USRPRF) as the Key to search the EFLDIST2 (physical file that holds address book information) file in the IDOCS695 and use the email address in field DIEMAILADR corresponding to the User Profile. If no email address is available or a bad email address, then the PCL output will be sent to the Invalid Mail Out Queue BADOUTPUT.
+In the Email Address Book we tie in the User Profile with the email address information by filling in the User Profile parameter in the address book record as shown in the example.
+{{pub:smartrouting:mapfield.png|}}