Skip to main content

Reporting issues resolved in KTA 7.7 Fix Packs


Question / Problem: 

What issues related to reporting have been resolved in KTA 7.7 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.

    • 1545044 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
    • 1530845 Case 26172354: [Reporting] extr_batch_sess_key reported after confirmation field
    • 1525492 Case 26172354: Reclassification affects field reporting data
      • Scenario 1: If a document is reclassified after extraction, such as in Validation, reporting data for fields of the previous type will persist and be associated with a document type that does not have those fields. This causes KAFTA reports to show fields that do not belong to the given document type.
      • Scenario 2: If a document is reclassified from a type where a field has “Include in analytics” is yes to a type where the same field has “Include in analytics” is no, then the reporting data for the field will persist. In KAFTA this causes this field inappropriately show up on a type where it isn't intended to be reported on. It also has the appearance of sporadic behavior, because it will only happen when the document is reclassified from a type where the field is reported on.
    • 1500871 Case 26157068: Reporting data: Original value and confidence not set    
    • 1496176 Case 26135941: extr_batch_ses_key isn't reported in field_accum_fact table 
    • 1469606 Case 26118747: Error during data extraction on message using reverted compressed flag: Invalid character in the given encoding 
    • 1468981 Case 26107596: Manual field change not reported as manual change if Kofax TotalAgility formatter modifies field value 
    • 1456228 Case 26084690: Reporting - Error PerformUpdates task - Execution Timeout Expired  
    • 1452943 Case 26099248: Kofax TotalAgility Classification Data Not Being Reported As Expected 
      • This issue occurs when Transformation Server is doing separation but is not able classify a document.  That document is not marked as system classified, so it does not get included in KAFTA reports.
    • 1373945 Case 25051197: [Reporting] The MERGE statement attempted to UPDATE or DELETE the same row more than once 
    • 1369122 Case 25064261: Reporting data stuck in WSA_MESSAGES table with error "TryDeserializeWithPatchingXml spent more than 1000 cycles"Broken messages caused infinite loop.Broken messages caused infinite loop  
    • *Bug 1361084:[Reporting] batch_sess_snapshot_fact includes incorrect information about number of pages after document merge



  • Was this article helpful?