How to: Troubleshooting Flex to DFWorks Issues

Product Feature: DFWorks

For your Consideration:
  • UniqueMailrunID  = Flex VendorID (Print Side ID)
  • DFWorks will match Flex data to MRDF header/MailrunID
  • Flex to DFWorks Workflow:
    • The job is submitted through Flex
    • Flex sends file transfer messages to DFWorks
    • DFWorks stores all data via FlexRawData Table
    • MRDF is created and sent to DFWorks 
    • MRDF header is updated by DFWorks and matched to the MailrunID enrolled in the Database
      • DFWorks updates the header with the UniqueMailrunID)
    • MRDF with updated header is submitted to the InsSte Importer
Process flow: 
The Flex Message to initialize the mailrun is received; all flex messages will be received in the FLEXRAWDATA Table (see D:\DFWorkslog\flex_xxxx.log). And the generatePrinterSpecPackets : generateFileTransferPacket function is invoked. This function generates the File Transfer packet and places it into the OPENSPEC_EVENTS table for further processing.

Using the DFWorks Quick Search to find the Mailrun  and confirm Flex messages
If you know the MailrunID or SourceID (typically the SourceID is the MRDF filename); enter  it in the DFWorks Quick Search
Quick Search
Click Details for the Tab views
If the Flex data is available via the Flex Tab, this means that DFWorks has  processed the Flex messages successfully (review data and make sure all needed events are present)
quick search a
Advanced Troubleshooting
Using queries to confirm DFWorks received & processed the Flex Message
(you can use the DFWorks SQL Editor)
Query Option (alternative to the DFWorks Quick)
select * from flexrawdata where jobname like '%123XYZ%' - The MailrunID is typically contained in the Jobname field
select * from flexrawdata where userparam13 = '123XYZ' - The MailrunID is typically in the userparam13 field
select * from flexrawdata where mailrundatafile = 'XYZ0000.TXT'  - Note that, not all flex records will contain a data file entry. However this query can be useful if all you have is the MRDF file name.  Also if you have access to the MRDF, the MailrunID will be contain in the MRDF.

No Data returned will indicate Flex Data was not received. Confirmed that every record has been processed by checking the Processed field for a "Y"
Confirmed the following events are present for the suspect Mailrun
EVENTACTION 32 - Start Incoming Transmission
EVENTACTION 33 - End Incoming Transmission
EVENTACTION 161 - Side Count from CHKR
EVENTACTION 184 - Current side count
EVENTACTION 64 - Page Count from CHKR
EVENTACTION 58 - Start Report        
EVENTACTION 66  - End Report Sides

Now Check the OPENSPEC_EVENT Table - This is table is what DFWorks rolls-up the Flex data to.
Observed EntryTime and ProcessTime. If Processtime is "Y" this means the Event has not been processed.
Open Spec Event

Query to note: 
select count (*) from Openspec_events where unprocessed = 'Y'  -  This query should return 0;Unprocessed records could be problematic.


UPDATED: April 27, 2018