pub:smartrouting
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
Next revision | |||
— | pub:smartrouting [2018/05/24 16:06] – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | |||
+ | < | ||
+ | |||
+ | ====== Smart Routing ====== | ||
+ | |||
+ | ===== Overview ===== | ||
+ | |||
+ | Smart Routing is a set of features in iDocs that permits the automatic routing of merged documents to Email, Fax or Print. It is implemented in two basic ways: | ||
+ | |||
+ | - The routing information can be retrieved from a database using spool file information as the database key, or | ||
+ | - The routing information can be scraped directly from the spool file. | ||
+ | |||
+ | ===== Smart Routing Using a Database ===== | ||
+ | |||
+ | The first step is to [[configuredatamap | create a mapped field ]] that contains the database key value. This for example might be a customer number if you are using a customer database file. From the main InFORM Decisions menu, take option one, Define a form or Check Application. | ||
+ | |||
+ | |||
+ | |||
+ | At this point, the left column of the screen should display the corresponding lines numbers of the spool file. Additionally the key value, such as the customer number, should be in full view. If the value is not in full view, the display screen may be shifted right by using the shift F8 key. | ||
+ | |||
+ | |||
+ | |||
+ | With the key value in full view, position the cursor in the leftmost position of the value and press the F8 key. Next, place the cursor in the rightmost position of the key value and press the F8 key again. This will display the Map Field Maintenance screen. | ||
+ | |||
+ | < | ||
+ | 5/ | ||
+ | | ||
+ | | ||
+ | Form Name. . . . . . DEMOINV | ||
+ | | ||
+ | Spooled File Source | ||
+ | From Row . . . . . . 1 To Row . . . . . . . 1 | ||
+ | From Column | ||
+ | | ||
+ | Overlay Target | ||
+ | Horizontal Position. 9998 300dpi | ||
+ | Map Field . . . . . | ||
+ | Font . . . . . . . . | ||
+ | Line Spacing . . . . | ||
+ | Form Side. . . . . . | ||
+ | | ||
+ | </ | ||
+ | |||
+ | Complete the field prompt by entering a field name and description. Choose any meaningful name for the mapped field – do not use a | ||
+ | keyword from the F4 prompt. Enter 9998 for both horizontal and vertical positions so the data does not print on the output page – those coordinates are off the pcl page. | ||
+ | |||
+ | < | ||
+ | Conditionally map | ||
+ | If the value in column | ||
+ | Map next field end | ||
+ | of this field . . . | ||
+ | Sort Sequence . . . . 1 F4=List | ||
+ | </ | ||
+ | |||
+ | |||
+ | Secondly, specify a sort sequence. | ||
+ | |||
+ | Bursting should be set to Y. This will create a new document and thus a separate transmission, | ||
+ | |||
+ | The normal procedure is to sort and burst on this field. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== Database Definition for Email ===== | ||
+ | |||
+ | Smart Routing considers output targets in this order: Email, Fax, Print. Any output method not defined will be skipped. The first method defined that successfully resolves a target destination such as an email address or fax number will be selected. If you need to handle customer preference as to delivery method use logical files to present to the Smart Routing application only one deliver method. | ||
+ | |||
+ | From the Form definition maintenance screen navigate back to the form application and place an option 14 next to the entry. Option 14 will be labeled External Database on versions older than 3.69d and Smart Routing on younger versions. | ||
+ | |||
+ | < | ||
+ | | ||
+ | 10: | ||
+ | |||
+ | Type information, | ||
+ | |||
+ | Application: | ||
+ | |||
+ | File Name . . . : ROUTINGDB | ||
+ | Library . . . : | ||
+ | Member Name . . : *FIRST | ||
+ | |||
+ | |||
+ | Prefix to key (if necessary) . . . . . : | ||
+ | Map field data to use as key . . . . . : MYSMARTKEY | ||
+ | |||
+ | String to return as *TOADDRESS . . . . : From Col: 10 To Col: 137 | ||
+ | |||
+ | Outq to receive file if *TOADDRESS not valid . . : BADOUTQ | ||
+ | |||
+ | </ | ||
+ | |||
+ | At this screen specify the file name and library of the database file containing the Smart Routing address information, | ||
+ | |||
+ | The next prompt identifies the location of the email address within the customer record. In the example above, the email address within the customer record begins in position 10 and ends in position 137 for a size of 128 characters. Please note that this is in bytes and is considered from the beginning of the record. It does not refer to fields in the database. | ||
+ | |||
+ | The last field specifies the location where the output spool files should be placed if the email address can not be retrieved, i.e. the lookup on the database using the specified key fails. If the lookup succeeds but the address is not deliverable, | ||
+ | |||
+ | Please note that in iDocs 5.0 and subsequent versions the address failure outqueue must be specified separately using option 18 from the [[defineform | main form list]] (subfile). | ||
+ | |||
+ | |||
+ | ===== Email Defaults ===== | ||
+ | |||
+ | From the iMAIL external routing screen the delivery parameters were specified for the recipient, but not the sender, subject and message body. These values can be specified by pressing the F6 key to specify the email default values. | ||
+ | |||
+ | < | ||
+ | 03/ | ||
+ | | ||
+ | | ||
+ | Type information, | ||
+ | | ||
+ | | ||
+ | | ||
+ | From: | ||
+ | To: | ||
+ | Subject: | ||
+ | | ||
+ | Message Default Line 1 | ||
+ | Message Default Line 2 | ||
+ | Message Default Line 3 | ||
+ | Message Default Line 4 | ||
+ | Message Default Line 5 | ||
+ | Message Default Line 6 | ||
+ | Message Default Line 7 | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | From this screen, enter the default from address, subject and associated text. Press the F10 key to save the values and return back to the form definition maintenance. | ||
+ | |||
+ | Note that one does not have to specify a default to address – that is determined as part of the Smart Routing processing. If you do not specify a default from address then the default contained in the iMail configuration will be used. | ||
+ | |||
+ | |||
+ | |||
+ | ===== Database Definition for Fax ===== | ||
+ | |||
+ | Navigate back to the form application and reselect it with an option 14. Press the F7 key to define the FAX directives. The screen below should be displayed. | ||
+ | |||
+ | < | ||
+ | 5/ | ||
+ | | ||
+ | | ||
+ | Type information, | ||
+ | | ||
+ | | ||
+ | | ||
+ | File Name . . . : ROUTINGDB | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | Map field data to use as key . . . . . : MYSMARTKEY | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | Outq to receive file if Fax# not valid . . . . . : BADFAX | ||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | The first five prompts for faxing should contain the same values for emailing. However if the fax number and email addresses are contained in different databases, these databases can be defined separately. | ||
+ | |||
+ | As specified previously for email, define the beginning and ending columns for the fax recipient’s company name, contact and fax number. | ||
+ | |||
+ | Finally in the last prompt on the screen specify the name of the out queue that will be used to collect spool files intended to be faxed, but resulted in not being faxed due to an invalid fax number. | ||
+ | |||
+ | If doing only Fax Smart Routing and not also email, use ***FAX** for the distribution outqueue in the form definition and *FORMDEF in the engine or manual merge. | ||
+ | |||
+ | ===== Fax Defaults ===== | ||
+ | |||
+ | Once all the values have been identified, press the F6 key to define the fax default values. | ||
+ | |||
+ | < | ||
+ | | ||
+ | 10: | ||
+ | |||
+ | Type information, | ||
+ | |||
+ | Application: | ||
+ | |||
+ | Cover Page : *DEFAULT | ||
+ | Fax Line . : *DEFAULT | ||
+ | |||
+ | From Company . . : inFORM Decisions | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | To Company . . : | ||
+ | | ||
+ | | ||
+ | |||
+ | F3=Exit | ||
+ | </ | ||
+ | |||
+ | From this screen specify the default cover page from within iFAX fax or override the default value. | ||
+ | |||
+ | |||
+ | |||
+ | The prompt for the Fax line specifies the default | ||
+ | |||
+ | The remaining entries for the from and to prompts will be used to populate the cover page with the correct inFORM Decisions of the sender and the recipient. | ||
+ | |||
+ | Press the F10 key to save this inFORM Decisions, and return to the Form Definition Maintenance Screen. | ||
+ | |||
+ | |||
+ | ===== Specifying the Out Queue ===== | ||
+ | |||
+ | |||
+ | |||
+ | From the Work With Form Applications subfile (list), scroll to the form application and place a 1 next to the entry. | ||
+ | |||
+ | < | ||
+ | 5/ | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | Front Map File. : | ||
+ | X adjustment value. . . . . . . . | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | Front Side Back Side | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | + | ||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | |||
+ | In the prompt for the Distribution Out Queue enter the key word value of either ***EMAILPDF** to process the distribution of the spool files in a PDF format, ***EMAILPCL** to process the distribution of the spool files in a PCL format. | ||
+ | |||
+ | Note that despite the keyword value being misleading and contrary to the alternative delivery methods, that if emailing is not an available option for the spool file, the alternate methods will be used. | ||
+ | |||
+ | ===== Engine Definition ===== | ||
+ | |||
+ | From the InFORM Decisions main menu, select option 4, Work with Engines. Select an existing engine, or create a new one dedicated to Smart Routing. | ||
+ | |||
+ | < | ||
+ | | ||
+ | 10: | ||
+ | |||
+ | Engine Name. . . . . . : DQENGINE | ||
+ | Archive Out Queue. . . : ARCHIVE | ||
+ | Data Queue . . . . . . : DQENGINE | ||
+ | Engine Status. . . . . : | ||
+ | |||
+ | | ||
+ | Prc Out Queue Library | ||
+ | Grp F4=List | ||
+ | QPRINT | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | | ||
+ | F3=Exit | ||
+ | Press Enter to confirm | ||
+ | </ | ||
+ | |||
+ | Changing the Destination Out Queue value to *FORMDEF specifies that the resulting spool file will be directed as it is defined in the form application. | ||
+ | |||
+ | In this example the form application named, JCAINV, has defined within it *EMAILPDF in the distribution override out queue. | ||
+ | |||
+ | After changing this value within the engine definition, the engine is ready to be submitted to batch and to process smart routing accordingly. | ||
+ | |||
+ | ====== Smart Routing Using Spool File Information ====== | ||
+ | |||
+ | The other way to use Smart Routing is to scrape the destination information directly from the spool file. Of course the information has to be in the spool file to scraped. Email addresses and fax numbers usually are not included in end user documents, but if they are this might be the simplest way to setup Smart Routing. | ||
+ | |||
+ | |||
+ | |||
+ | The procedure is to create a form application as one normally would, and then in addition to the mapping for the output create additional mapped fields as discussed below. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== iMail ===== | ||
+ | |||
+ | |||
+ | |||
+ | For email routing, create mapped fields named using the following keywords containing the specified information. | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | ***FRADDRESS** – iMail from address. | ||
+ | |||
+ | < | ||
+ | |||
+ | ***TOADDRESS** – iMail recipient address | ||
+ | |||
+ | < | ||
+ | |||
+ | ***CCADDRESS** – iMail recipient address to copy | ||
+ | |||
+ | < | ||
+ | |||
+ | ***BCADDRESS** – iMail recipient address to blind copy | ||
+ | |||
+ | < | ||
+ | |||
+ | ***SUBJECT** - | ||
+ | |||
+ | < | ||
+ | |||
+ | ***SUB0120 ** - iMail Subject 1 through 20 | ||
+ | |||
+ | < | ||
+ | |||
+ | ***SUB2140** - iMail Subject 21 through 40 | ||
+ | |||
+ | < | ||
+ | |||
+ | ***MESSAGE** - iMail Message | ||
+ | |||
+ | < | ||
+ | |||
+ | ***MSG01** - **09** - iMail Message lines 1 through 9 | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | You can prompt the field name in the greenscreen mapped field screen, scroll through the possible keyword values, and select one of the above. | ||
+ | |||
+ | |||
+ | |||
+ | To successfully define a Smart Routing email application from the above keywords as mapped fields you must define at a minimum *TOADDRESS. | ||
+ | |||
+ | In the form application definition the destination outqueue is *EMAILPDF. The destination outqueue in the engine is *FORMDEF. | ||
+ | |||
+ | **Note on Subject Line:** | ||
+ | |||
+ | You can create a “dynamic” subject line in your EMAIL that will contain information mapped from your spoolfile. | ||
+ | |||
+ | * The *SUBJECT keyword replaces the default subject line defined in Smart Routing. | ||
+ | * The *SUB0120 and *SUB2140 keywords append to the default Smart Routing subject. | ||
+ | * Each allows up to 20 characters and can be used together, but *SUB0120 must be defined before using *SUB2140. | ||
+ | |||
+ | Example: | ||
+ | < | ||
+ | From | ||
+ | Fld Name Description | ||
+ | *SUB0120 | ||
+ | *SUB2140 | ||
+ | </ | ||
+ | Subject: Default Message +First mapped field+ +Second field+ | ||
+ | Email subject default = ' | ||
+ | First mapped field (*SUB0120) = ' | ||
+ | Second mapped field (*SUB2140) = ' | ||
+ | |||
+ | |||
+ | ===== iFax ===== | ||
+ | |||
+ | |||
+ | |||
+ | The iFax interface to mapped field Smart Routing is identical to that of iMail. The keywords used to name the mapped fields are different. They are: | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | ***FAXNBR** - iFAX FAX Number | ||
+ | |||
+ | < | ||
+ | |||
+ | ***FAXDESC** - iFAX FAX Description | ||
+ | |||
+ | < | ||
+ | |||
+ | ***FAXNBRUSR** - iFAX FAX Number User Data | ||
+ | |||
+ | < | ||
+ | |||
+ | ***FAXTO** - iFAX FAX Recipient | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | To define an iFax Smart Routing application using this method one must define at a minimum *FAXNBR. | ||
+ | |||
+ | |||
+ | |||
+ | In the form application the destination outqueue is *FAX; in the engine it is *FORMDEF. | ||
+ | |||
+ | |||
+ | |||
+ | ===== Print ===== | ||
+ | |||
+ | |||
+ | |||
+ | To define print as the Smart Routing destination define a mapped field with field name: | ||
+ | |||
+ | |||
+ | |||
+ | ***OUTQ** - iDocs Out Queue | ||
+ | |||
+ | |||
+ | |||
+ | The contents of the mapped field will be evaluated and its contents used to specify the destination outqueue of the resulting merged document. | ||
+ | |||
+ | The output outqueue in the form definition is specified as *PRINT. | ||
+ | |||
+ | |||
+ | You can also define mapped fields to capture: | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | ***TRAY** - iDocs Input Tray | ||
+ | |||
+ | < | ||
+ | |||
+ | ***BIN** - | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | ---- | ||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
pub/smartrouting.txt · Last modified: 2022/06/25 17:02 by 127.0.0.1