Skip to main content
Kofax

Reporting issues resolved in KTA 7.6 Fix Packs

3024495

Question / Problem: 

What issues related to reporting have been resolved in KTA 7.6 Fix Packs?

Answer / Solution: 

The following reporting issues are included in the release notes of the listed fix pack (unless noted with *).  If encountering an issue with reporting, it is best to update to the latest fix pack so that all cumulative fixes are applied.

 

  • 7.6.0.14
    • 1582420 Case 25043583: The DELETE statement conflicted with the REFERENCE constraint
  • 7.6.0.13
    • 1572973 Case 26239055: Field changes do not show up in Kofax Analytics for TotalAgility 
      • Introduced by the “Reclassification affects field reporting data” fix,  PDF/DC/IP activities inappropriately changed fields to be reported as “system extracted”, thus field_accum_fact.field_recog_status_key was set incorrectly, and so fields did not show as changed in KAFTA reports.
    • 1567486 Case 26239055: Field Reporting data can be lost after PDF/DC/IP activities
      • Introduced by the “Reclassification affects field reporting data” fix,  PDF/DC/IP activities inappropriately report that no fields are present, thus even if a current field value is reported again by a subsequent activity, it would have lost reporting data such as original value, confidence, etc.
    • 1564434 Case 26218684: Reporting performance issue with doc_accum_fact table    
    • 1558019 Case 26193760: Reporting: Problematic messages causing ETL to complete without processing any messages
    • 1545038 Case 26176670: Duplicate entry in Reporting tfs_class_dim table causes Reporting ETL failure “The MERGE statement attempted to UPDATE or DELETE the same row more than once
    • 1543501 Case 26189941: Error during data extraction on message using reverted compressed flag: Invalid character in the given encoding
    • *Bug 1569860:[7.6.0.13] [Reporting] 'Error mapping data row MapStatusKcDocField ' occurs in Reporting log
  • 7.6.0.12
    • 1530841 Case 26172354: [Reporting] extr_batch_sess_key reported after confirmation field  
    • 1525466 Case 26172354: Reclassification affects field reporting data    
    • 1500866 Case 26157068: Reporting data: Original value and confidence not set
  • 7.6.0.11
    • 1496173 Case 26135941: extr_batch_ses_key isn't reported in field_accum_fact table
  • 7.6.0.10
    • 1456225 Case 26084690: Reporting - Error PerformUpdates task - Execution Timeout Expired 
  • 7.6.0.7
    • 1373941 Case 25051197: The MERGE statement attempted to UPDATE or DELETE the same row more than once 
    • 1369119 Case 25064261: Reporting data stuck in WSA_MESSAGES table with error "TryDeserializeWithPatchingXml spent more than 1000 cycles" 
  • 7.6.0.5
    • 1329910 Case 25056955: Confirming table cells without modification shows as a changed field
    • 1346512 Case 25063733: Wrong config for “Include in Analytics” is saved to Database
    • 1346236 Case 25063733: Bug Extraction Group: wrong config for “Include in Analytics” after importing in 7.6 
  • 7.6.0.2
    • 1296396 Case 25040509: Arithmetic overflow error converting IDENTITY to data type int 
    • 1299453 case 25034013: Some reported field should contain the symbols which are not allowed in XML 

 

 

  • Was this article helpful?