#KTA Fix Pack ,#TTA Fix Pack #Tungsten TotalAgility Fix Pack
TotalAgility 7.11 Fix Packs – All
Fix Pack 27 – 3rd Apr 2025
| Component | Issue |
|---|---|
| Web service | When saving the SOAP web service that used a client certificate, the following error occurred: “A secure SSL/TLS channel could not be established.” |
| Form | The behavior of the Radio button list control changed between TotalAgility versions 7.8 and 7.11, specifically when the Changed Event was triggered and the “Clear Selection” action was used. |
| Form | There was a difference in the behavior of the Radio button list control between TotalAgility versions 7.8 and 7.11. |
| Process | When more than two work type fields were mapped to a Dynamic complex variable within the business rule, the following error occurred: “Index was outside the bounds of the array.” |
| Transformation | The documents rejected by the Transformation Server were not logged in the reporting table. |
Fix Pack 26 – 6th Mar 2025
| Component | Issue |
|---|---|
| Form | Blind double keying failed during validation on the third and subsequent documents because empty values were not recognized. |
| From | When a calculation rule was created in a form and specific categories were filtered to add different global variables, some of those variables did not display correctly after the rule was validated. |
| Reporting | The data from the documents was not displayed in Kofax Analytics for TotalAgility. |
Fix Pack 25 – 6th Feb 2025
| Component | Issue |
|---|---|
| Installer | The silent installation of the separate license server fix pack failed and required Internet Information Services configuration. |
Fix Pack 24 – 16th Jan 2025
| Component | Issue |
|---|---|
| Form | When a condition was used in the form, the decimal delimiter did not work. |
| Process | The Blind Double Keying process failed on the second document, allowing empty values to be accepted. |
| Scan | Could not perform scanning via the flatbed using a Kodak S3100f scanner with a flatbed accessory when using TotalAgility. |
| Transformation | An error occurred when the Online Learning folder was locked during the document deletion process. |
Fix Pack 23 – 12th Dec 2024
| Component | Issue |
|---|---|
| Process | The jobs were suspended with the following error: “The process cannot access ‘XYZ.dll’ or one of its dependencies because it is currently in use by another process.” |
| Transformation | Document extraction failed due to exceeding data egress limits from a low retry interval, resulting in request failures. |
| Form | TotalAgility application became unresponsive, and an error appeared when confirming the last field with actions on the form multiple times. |
| Process | The KCM (Kofax Communication Manager) compose activity was suspended when the process map was configured to run in synchronous mode. |
| Core Worker | In a TotalAgility production environment with a large number of tenants and CoreWorker load, .Net or Capture activities sometimes failed with errors. |
| Installer | The installation of the TotalAgility 7.11 fix pack failed with the “Violation of Primary Key Constraint” error. |
Fix Pack 22 – 7th Nov 2024
| Component | Issue |
|---|---|
| CoreWorker | In a TotalAgility production environment with a large number of tenants and CoreWorker load, the .Net or Capture activities sometimes failed with errors. |
| Transformation Desginer | In the Transformation Designer, the extraction results for a sample document encountered errors. |
| Web Capture | When Canon scanner with Kofax Web Capture was used for scanning in TotalAgility, an error occured during the scanning process. |
| SDK | SQL injection vulnerabilities or database errors were observed when sending a SOAP request to the UpdateDocumentVariant SOAP action in the CaptureDocumentService. |
Fix Pack 21
| Component | Issue |
|---|---|
| Process | When an exception was raised during the execution of RPA (Robotic Process Automation) activity, the TotalAgility job was completed without any errors, instead of getting suspended. |
| Process | In a process, the Subject and Body fields for all Email activities appeared empty. |
| Transformation Designer | In TotalAgility Designer, when federated security was configured to use the “TotalAgility and the Provider logout” option with the endpoint type set to SAML, an error occurred upon logout. |
Fix Pack 20
| Component | Issue |
|---|---|
| Reporting | The Reporting process failed with the following error: “Cannot insert duplicate key in object ‘dbo.@p'” |
| Reporting | An error occurred when reporting tried to add duplicate entries to the “doc_accum_fact” table. |
| Import Connector | When the seed value for “BinaryObject.Id” exceeded the maximum integer value, an error occurred when the messages were transferred from the Import Connector to TotalAgility. |
| Form | When an Activity form was regenerated on a process that contained the input and output variables, the following error occurred “ Index must be within the bounds of the list.” |
| Reporting | When an API call was used to classify documents in TotalAgility, the Category and Classification group displayed as ‘Not Set’ in Kofax Analytics for TotalAgility. |
| Process | Database timeout occurred when large data was added to the TotalAgility database as part of the JobEvaluation worker task. |
| Process | The PDF/A generated with file attachment did not comply with the PDF standard. |
| Transformation Server | Could not perform recognition due to an internal OmniPage error. |
Fix Pack 19
| Component | Issue |
|---|---|
| Form | In a Scan create new job form, when a document was split into two, downloading either document resulted in the “value cannot be null” exception. |
| Form | When a DB query action was used in a multi-line text box to manage database records, a null value was returned, and an error occurred. |
| Conversion | The document conversion failed when certain documents were converted to “PDF/A-2b” or “PDF/A-3b”. |
| Transformation | In a format locator, if two keywords with the same value were defined, a confidence level of 0% was returned. |
| Packaging | ImportPackageFromStream in custom code resulted in an “object reference has not been set to an object instance” error for large packages. |
| Form | The following error occurred in a Validation activity: “Cannot insert duplicate key object ‘dbo.@valuesTable’. The duplicate key value is (XXX)when a processing job.” |
| Conversion | When a process was configured with an Image processing activity, converting the text files to Tiff caused font and alignment issues. |
| Transformation Designer | When the extraction group was opened in the Transformation Designer, an error occurred.. |
| Import Connector | When the Import Connector was configured to poll the messages, the polled messages were moved to the processed folder but remained unread instead of being marked as read. |
| SDK | The encryption of ImageID was not added to all SDK methods, that resulted in the usage of the same URL to view multiple images. For more details, |
Fix Pack 18
| Component | Issue |
|---|---|
| Form | When the backtick (`) character was used in a field, this special character was added and merged with the next digit or letter, making it difficult to view it in the field. |
| Transformation | Could not perform Tungsten Transformation Toolkit Online Learning on a folder. |
| Form | When a skin was used, the new Validation form assigned to the process or skin was not used after modification and regeneration. Instead, the old Validation form was retained. |
| Process | When a document variant was used during validation and specific table columns were ignored, this resulted in the table not being valid at runtime, and the activity could not progress. |
| SDK | When the CreateJobSyncWithDocuments() was used against an RTTS instance pointed to the Azure tenant, the job was suspended with an index error. |
| Package | When a package that contained the currency codes was imported, the Artifact filter did not work. |
| SDK | The ActivityService.GetWorkqueueOverview API timedout with a relatively low number of jobs, especially when additional activity resources were added. |
| Transformation | The following error occurred when Adavanced Zone Locator was used: “Fox-Exception: Index (127) out of range (0 – 126).” |
| Scanning | Could not perform scanning via the flatbed using a Kodak i3400 scanner with a flatbed accessory when using TotalAgility. |
| Conversion | The attachments names were missing from the ‘Body’ document after conversion. |
| Form | The global variable, “Job ID” was not set after it was used in an action and saved. When the action was reopened after being saved, the “Job_ID” global variable was replaced with the form control of the same name. |
| Import Connector | When there were multiple RightFax connectors, there was a delay importing the RightFax files into TotalAgility. |
| Transformation | The document for online learning was missing page images and a source file, which led to processing errors. |
Fix Pack 17
| Component | Issue |
|---|---|
| Form | In a Scan form, the control layout did not work when the form was loaded. |
| Form | The carriage return (\r) and line feed (\n) characters did not work correctly in TotalAgility. |
| Transformation | The Advanced Zone Locator encountered the “Fox-Exception Index out of range” error, which caused the Extract activity to fail, and resulted in the suspension of the job. |
| Reporting | When the debug.txt file existed, it caused the ETL process to become unresponsive with high CPU, and no logs were written. |
| Process | The connection string server variable was updated three times in a Data Access (DAS) activity even though the variable was not used as an output. |
| Conversion | In a Document conversion activity, certain documents failed while conversion, and the activity was suspended with an error. |
Fix Pack 16
| Component | Issue |
|---|---|
| Form | When a job was created using the out-of-the-box CreateNewJob form, the following error occurred: “The maximum length for this field is 0”. |
| Coreworker | The settings that control the automatic clean-up of the “Generated Documents” folder were not available in the configuration file. |
| Form | When an Activity form was regenerated on a process that contained the input and output variables, the following error occurred “ Index must be within the bounds of the list.” |
| Reporting | The “DeleteMachineDim” query, which was responsible for deleting machine dimension records as part of the reporting retention process, timed out. |
| Form | An issue occurred when a search was performed within the dropdown lists contained in the Capture table cells of the Choice type field. |
| Process | In a Document creation activity, all the fields were not detected when the document templates contained merged fields. |
Fix Pack 15
| Component | Issue |
|---|---|
| Coreworker | The settings configured to clean up the temporary files in the generated “Documents” folder did not work in a TotalAgility Azure environment. |
| Installer | When the “initializedata” path under “TraceListener” was customized in the configuration file of an earlier version of TotalAgility, the installer could not merge the new trace listener when upgrading to TotalAgility 7.11. |
| Web Capture | The tooltip was not displayed for a sticky note in a Web capture control. |
| Package | When a package that contained the currency codes was imported, the Artifact filter did not work. |
| Form | In a Validation form, when all fields in the first document were confirmed, the focus did not shift to the second document, and the form became unresponsive. |
| Package | When a package was created that contained the custom service, the web service data was not displayed on the Deployment configuration tab. |
| Transformation | For a project in the Transformation Server that had Online Learning enabled, an issue occurred with Transformation Server Cloud Online Learning. |
Fix Pack 14
| Component | Issue |
|---|---|
| Workspace | Due to the timing issue, the Work queue query columns were reset and not used as defined in the Work queue query. |
| Installer | The MSI installer of TotalAgility Web Capture Service used an obsolete version of Visual C++. |
| Form | The date formats displayed in both rows differed when the same date was passed on to two rows. |
| Form | The table columns were not available in a Display rule action at runtime. |
| SDK | When “UpdateDocumentTypeWithConfidence” was used to set a document type with the previously recorded confidence value, the confidence value was not retained. |
| Package | When a package that contained the Currency codes was imported, the Artifact filter did not work. |
| Form | The search displayed an incorrect option in the drop-down list for a table column in the Capture forms. |
Fix Pack 13
| Component | Issue |
|---|---|
| Web Capture | When the documents were scanned using scanners via Kofax Web Capture and Scan Agent, the Web Capture scanner settings were reset to default whenever a new scan was initiated. |
| Transformation | The Kofax.CEBPM.DocumentConversionService.Host.exe process did not start correctly. This may cause issues when the Transformation Server processes the Document conversion activities. |
| Transformation Designer | In the Transformation Designer, when extraction was performed on the documents, a few PDFs returned the “Fox-Exception” error. |
| Upgrade Installer | On upgrading to Kofax TotalAgility 7.10, the following error occurred in a Web service activity: “Object reference not set to an instance of an object.” |
| Form | The Refresh capture form action behavior was different in Kofax TotalAgility versions 7.10 and 7.11. |
| SDK | The PackageStreamingService SDK APIs did not work as expected when using the default URL endpoint (the JSON URL endpoint is no longer supported). |
| Conversion | The Document conversion failed if the “Enable portfolio PDF file extraction” setting was enabled in a Document conversion profile. |
| Import Connector | The PDF attachments were corrupted after Message Connector downloaded an email. |
| Process | When a new PDF was generated after validation, all the fields were not converted into the new PDF, and the PDF was incomplete. |
Fix Pack 12
| Component | Issue |
|---|---|
| Form | The search criteria in a DAS action were automatically reordered instead of retaining the order. |
| Form | When the browser language was set to German, the default value of a Float variable was changed. |
| Transformation | When the FormXtra profiles were used in combination with profiles from other engines in the Advanced Zone Locator, the warmup, and cleanup times for the FormXtra process took longer time. |
Fix Pack 11
| Component | Issue |
|---|---|
| Form | The Refresh Capture form action was different in Kofax TotalAgility versions 7.10 and 7.11. |
| Form | Dates returned to form controls changed unexpectedly. |
| Workspace | Job and Work queue queries failed after upgrading to 7.10.0.22 and using @today in criteria. |
| Conversion | Document Conversion split MSG and EML files into multiple documents. |
| Device | The database was affected when the KFS_DEVICE table was blocked. |
| Import | The RightFax REST API did not retrieve the recipient’s fax number when forwarding a fax from one user to another. |
| Transformation Designer | Transformation Designer failed importing locator. |
| Transformation | The Transformation Server service loaded the complete hierarchy for each document, resulting in exponential memory usage. |
| Transformation | Kofax Clarity Optical Character Recognition did not connect to the libcurl library. |
| Form | The Document review activity form was not created if a custom service was used in the process map. |
| SDK | The Kofax Total Agility Cloud – TEMP user folders were not removed after the account was deleted. |
| Transformation | Only the first page of the detected tables was available in the repository after extraction. |
| Import Connector | An issue with MS Graph multi-instance mode caused duplicate emails to be imported into Kofax TotalAgility when using Shared Message Connector. |
| Process | The embedded content was missing in the emails forwarded to Kofax TotalAgility from an Android device. |
| Conversion | PDF conversion failed if the PDF contained the Code-39-25 font. |
| Device | Excessive updates to KFS_DEVICESESSION from Management Frame Protection Client prevented users from connecting to the server. |
| SDK | The ResourceService SDK method, DoesResourceExist, suspended the job if the resource was not found. |
| Import Connector | Message conversion failed using IMAP if the Include message header of email and embedded email(s) option was selected in Import settings. |
| Transformation | The Registration checkbox was missing in the Anchoring properties of the Advance Zone locator. |
Fix Pack 10
| Component | Issue |
|---|---|
| Process | On upgrading to Kofax TotalAgility 7.11.0, the rule defined in a skin was changed. |
| Form | A blank window appeared in a Validation activity when the Vendor Search button was clicked in Kofax AP Agility. |
| Form | The Create new job activity failed to return the job ID. |
| Authentication | In the Kofax TotalAgility federated security system, the HTTP-Post SAML token request was incorrectly accepted as Get request. |
| Process | When a process was copied, the Export activity incorrectly used the original process ID instead of using the ID of the new process. |
| Transformation | In a Transformation project, the Data Matrix barcodes were not detected. For more details, see Additional information. |
| Form | An issue occurred when the DocumentFormLoaded event that contained a few actions modified the document and these actions were intersected with other calls that the Capture form performed during loading of the documents. This caused the outdated data to be stored in the cache. |
| Import Connector | The connection with Message Connector failed as Kofax TotalAgility Designer did not save the Process password correctly. |
| Web service | An Object Reference error occurred on a web service reference that used both HTTP and HTTPS bindings. |
| Process | A .Net activity was suspended with an Object Reference error when the method had an array output parameter. |
| Process | When the job was created on a process with multiple embedded activities, the names of activities were incorrectly displayed when viewed in a job. |
| Form | The Tab control on a Validation activity form failed to load when the Validation activity was opened for the second time. |
| SDK | In a Real Time Transformation server (RTTS) installation of Kofax TotalAgility On-Premise Multi Tenant, when the CreateJobSyncWithDocuments() method was executed to create a synchronous job on the process, the .Net activity returned the following error: “Value cannot be null. Parameter name: bytes.” |
| There was an issue importing the error codes. | |
| Package | The field zoom settings created via package import were retained and added to the DATA_XML column of the CAPTURE_DOCUMENT_TYPE table even after getting deleted via TotalAgility Designer. |
| Import Connector | Test Mailbox and email polling returned “Invalid client secret provided” error in the case of MS Graph only with Resource Owner Password Credentials (ROPC) grant. |
| Coreworker | The live activity records from the TotalAgility LIVE_ACTIVITY table were not deleted once the activity was taken or locked. |
| Transformation | The Code128 barcodes were not recognized. |
| Transformation | In a document with multiple barcodes, all the barcodes were not detected. |
| Transformation | The Code39 barcodes were incorrectly recognized and the results varied depending on the “Kernel.Ocr.BAR.Bar1D.MinLength” setting. |
Fix Pack 9
| Component | Issue |
|---|---|
| Process | Documents were duplicated with the same GUIDs. |
| Package | When a package was imported, the security roles were not associated with their category and were incorrectly set to the default category. |
| Installer | On installing the Kofax TotalAgility Fix Pack 7, the process could not be copied. |
| Import Connector | The conversion of German characters failed when the messages were processed using the MS Graph import source. |
| Package | When a package was compared before deploying it to the deployment server, the following error occurred: “Invalid Target URL. Please provide a valid Target URL.” |
| Form | As issue occurred with navigation and form display when the form fields were copied from one form to another. |
| Process | When a job was created on the process, the job was suspended with the following error: “Resolution failed with error: No public constructor is available for type Agility.Server.Core.Model.Interfaces.Services.IJobDebugService.” |
| Import Connector | When a Message Connector configured with the RightFax REST API was connected to the RightFax server, the connection failed, and the Message Connector got disconnected. |
| Workspace | In a TotalAgility WorkQueueForm that used the GetWorkQueue2 method, the “Refresh”, “Back”, and “Next” buttons did not work as expected. |
| Import Connector | When a Message Connector was configured with the RightFax REST API and connected to the RightFax server in a multi-instance mode, the faxes remained forever in the RightFax inbox without being imported. |
Fix Pack 8 – 28th Sep 2023
1998299, 26772184: The RightFax import source password was incorrectly saved in the TotalAgility database.
1997514, 26766556: When the browser language was set to German, the default thread pools were translated when the UpdateServerSettings4() method was called.
1990419, 26749658: The incoming request had more than a maximum of 2100 parameters supported by the server.
1989659, 26760323: In a Scan activity, the “Auto-navigate to next rejected page/document on rescan” option did not work.
1989337, 26721563: In a Dropdown list control, the GUIDs were displayed instead of values when the data was populated from a custom database.
1987251, 26715588: There was an issue detecting the Datamatrix barcodes.
1985984, 26759684: While exporting a package in TotalAgility, the following error occurred: “Transaction scope nested incorrectly.”
1985312, 26755911: When Business Rule Logging was disabled, the job was suspended and the executor returned the following error: “Execution of the activity failed. Unable to find Variable.”
1985107, 26750275: In a .NET activity, the following error occurred on the execution of the GetActivitiesWithQuery2 API: “User does not have sufficient access rights on the query.”
1938721, 26666295: When Unicode characters were used in a PDF, the following error occurred: “Unknown error in FoX library occurred: There is no mapped character in the multibyte code page for the Unicode character.”
Fix Pack 7
1987222, 26743150: When the document barcodes were assigned to a data model variable, the job was suspended with the following error: “Invalid JSON data.”
1986686, 26758061: The database error occurred in a Docker installation as the MACHINE_NAME column length in the Kofax TotalAgility tables was inconsistent throughout the TotalAgility databases.
1986508, 26758330: If an Export activity was used within a subjob, the job was suspended with an error.1984047, 26718512: The images were not loaded on the forms.
1982594, 26748341: When converting the Word documents to PDF/A2b using document conversion, some of the pages failed to display the footer information.
1982334, 26699565 , 26738857: When the Export Connector was installed on TotalAgility 7.11.0 that used HTTPS with Windows Authentication mode and SSL enabled in the IIS, the Export Connector installation failed with the following error: “The HTTP request was forbidden with client authentication scheme ‘Negotiate’.”
1982281, 26732718: The Multifactor authentication (MFA) login failed when a user logged on to two different browsers on the same computer or two different browsers on two computers.
1982243, 26750819: The loading time of a new form version took more than 20 seconds.
1982238, 26734153: The renamed categories appeared twice in the Reporting database.
1981903, 26713109, 26745359: In the RPA activity, the Boolean variable value was not updated if the returned value was true.
1981205, 26701283: When the Fix Pack 5 was applied on Kofax TotalAgility 7.11.0, the images were not displayed in the Transformation Designer.
1980813, 26732382: The “/” character used in a date was incorrectly recognized by the OmniPage when the recognition language was set to French.
1980807, 26596347: “The Merge page PDF data” option in a PDF generation activity prevented optical character recognition on demand for PDF generation.
1979309, 26685962: When you imported a file (greater than 2GB) with the blob storage type set to SQL Server, an empty document source was created instead of the file getting rejected.
1979270, 26746075: When the GetResources() method was used to get the resources, it took longer than the expected time and the performance issue occurred.
1977817, 26720437: When a process that contained a role was copied, the copied process failed to create a new role ID.
1977805, 26740115: The Validation form became unresponsive when a fuzzy search was performed.
1976817, 26636186, 26721177, 25023467: The installation of Kofax TotalAgility 7.11.0.5 fix pack failed with the following error: “Illegal characters in path.”
1976510, 26737095, 26736373: In the Transformation Designer, FineReader was incorrectly used during PDF generation.
1963650, 26701709: When comparing two packages, if a scroll bar was used to scroll the lists of both packages and compare all artifacts from the two packages displayed side by side, the artifacts on the left and right sides were not aligned.
Fix Pack 6
1979111, 26738342: The processing of Web Services Addressing (WSA) messages failed with the following error: “Cannot insert duplicate key in object ‘dbo.@p’ (OrmRejectNote).”
1977830, 26672813, 26741291: When a form with the File upload control was opened at runtime without logging in to TotalAgility Workspace, the file upload failed with an error.
1977176, 26731265: Mapping a Text box field to a Fuzzy search action caused the action to fail at runtime.
1976831, 26639677: An error occurred when loading the Monitor Workload form if the resource did not exist.
1976582, 26684950: If the VB.net script was used as a field validation rule in the business rule, the rule failed intermittently with an error.
1974972, 26735588: When an Expression activity was used to populate the data object with a string starting with the “[” character, the job was suspended at Expression activity with the following error: “Invalid JSON data. {0}.”
1974931, 26735488: The job was suspended at the Document conversion activity with the following error: “Document source missing sufficient file type information.”
1973365, 26686693: The OmniPage engine did not recognize the “<” character correctly.
1972861, 26718934: When configuring a new database connection in the Kofax Transformation Designer, an error occurred on entering the connection string.
1972262, 26732646: Kofax TotalAgility Designer became unresponsive when loading a large number (more than 90,000) of resources.
1972253, 26721344: When the AddWorkerResource4() method was used to add the resources to a group, the performance issue occurred.
1971724, 26715588: The OmniPage Barcode Locator did not recognize all Data Matrix bar codes. For more details, see Additional information.
1971260, 26718949: When a business rule with an Expression activity was exported with the variable value set to “Error code message”, the value changed to Static on import.
1970944, 26730049: When the browser language was set to German, the DB query actions were not executed successfully.
1970935, 26711902: The “Check for database compatibility” option did not work as expected when installing a fix pack in an On-Premise Multi-Tenant environment.
1970445, 26721196: When mapping a SharePoint site to a SharePoint add item activity, the following error occurred: “The attempted operation is prohibited because it exceeds the list view threshold.”
1969405, 26713610: The changes made to the extraction group were not saved in the Kofax TotalAgility Designer.
1969382, 26719658: The RESTful web service requests with URL parameters failed.
1968510, 26713057: There was a Cross-site scripting vulnerability in a Work queue control.
1967425, 26705905: When the TotalAgility database became accessible again (usually within two minutes) after becoming inaccessible due to failover to another node, the CoreWorker failed to progress on activities.
1549468, 26207051, 26366698, 26559290, 26729846: When the DataBase Locator with Kofax Search and Matching Server returned a confidence value greater than 100%, an error occurred.
Fix Pack 5
1968941, 26698657: In a drop-down list with a style set to Inline, the values in the second column were incorrectly aligned to the left instead of the right.
1968517, 26715454: The GetImportConnection and GetImportConnection2 methods returned credentials to the caller of the import connections API.
1967325, 26702279: The line break did not work as expected when a Dynamic complex variable was mapped to the template placeholder.
1967158, 26678409: The Message Connector became unresponsive when trying to convert the documents for a certain period of time.
1965767, 26709726: An error occurred when executing the post-upgrade scripts on the OPMTDBUpgrader utility.
1964390, 26698958: When the Mixed Print recognition engine was used for classification in the Transformation Designer, the following error occurred: “There was an error reading from the pipe. The pipe has been ended.”
1963653, 26709592: When a package was created on a process that used skins, the package failed with an error.
1963368, 26707776: Registration of the zone did not work in the Area Zone Locator.
1963193, 26701283: When extracting text from a PDF document. the combination of Arabic and English text in a single field caused alignment issues.
1963183, 26705918: The Table model assigned to a field in the Transformation Designer changed after the extraction group was released in TotalAgility Designer.
1963109, 26699314: The business rule execution failed when a Dynamic complex variable was passed as an input value.
1962879, 26703461, 26717472: The Data Matrix 2D bar codes were not detected when the “GS1-128” bar code type was enabled.
1961579, 26679245: When a Document conversion profile was used with the “Create PDF for capture input” option enabled, there was missing data in the exported PDF.
1960387, 26702698: Microsoft Visual C++ 2003 Redistributables in Kofax TotalAgility install files for Image Reader in Transformation Designer were outdated.
1959747, 26695480: The table Locator caused a memory leak issue.
1953184, 26682191: If an email body had special characters, then those characters were not saved correctly when the email body was mapped to a String initialization variable in Kofax TotalAgility.
1953178, 26676429: In the Import Connector, the German letters were not displayed when converting .log or .txt files.
Fix Pack 4
1955716, 26684602: Could not tab to a Calendar control on a Validation form.
1955644, 26685851: When the TypeAhead feature of a Choice Combo box Capture field was used, on pressing the Enter or Tab key, the item selected was incorrect.
1955421, 26680180: The updated data could not be loaded in Kofax Analytics for TotalAgility as etl_job_key was not updated.
1955415, 26679898: The “Invalid Session ID” error occured when trying to access the TotalAgility Workspace using custom code.
1954939, 26690360: The exported PDF did not contain annotations and masks.
1954698, 26688398: The following error occurred on a separate Web and Application server: “Method UpdateDocumentFieldPropertyValues is not supported on this proxy.”
1954245, 26688551: The child job was suspended at a node with “Invalid job state error” when the original process was at the decision node at runtime.
1953967, 26690832: The PDF compression was not used when a document had a mix of pages with and without PDF page data.
1953322, 26704682: The images from the Kofax TotalAgility database were not displayed in the TotalAgility forms.
1949606, 26679803: There was a discrepancy between the number of users logged on to Kofax TotalAgility and the concurrent user licenses consumed.
Fix Pack 3
1951690, 26690275, 26695160: When a Cloud tenant accessed other tenants’ deployed folders, issues such as “The specified site does not exist” occurred.
1951026, 26685314: When you configured the Design properties for a Table control, and the style was set to be inline, the style was ignored in the debug mode.
1946742, 26681341: The Document type drop-down did not filter correctly when typing the document name.
1946728, 26679533: Barcode 39 was not recognized by the OmniPage Barcode Locator.
1944593, 26662588: The Validation form became unresponsive when redirected to the next document.
1944581, 26673373: A white space was added to the Kofax TotalAgility Capture table under certain conditions.
1943482, 26674176: When testing a Check Locator in Transformation Designer, the following error occurred: The process was terminated due to an unhandled exception.
1943471, 26662929: An error occurred while converting the image to black and white during the training of the document.
Fix Pack 2
1942370, 26668673: On the Integration Server where a TIFF image with larger files was imported through a Kofax Import Connector, the Watched folder resulted in a 0-page document at runtime.
1942025, 26653392: When the Integration server was in a different time zone, the System tasks’ due dates were updated incorrectly slowing down the processing speed of the CoreWorker.
1941332, 26670527: If “Provider” was used as a prefix in the database name, the connection to the TotalAgility database failed with the following error: “DAS Database information retrieval failed.”
1941325, 26584370: An issue occurred when loading a popup window in the Activity forms.
1940954, 26667959: When a drop-down list was used in the search criteria of a DB query action, and the drop-down did not have a default value, or a value selected, the following error occurred: “Please provide a valid Numeric value.”
1940225, 26661067: The “Name template” property of a document type did not work when the documents were created using the following Capture SDKs: CreateDocument3(), CreateDocuments2(), CreateDocumentWithPages() and CreateDocument()..
1938548, 26655795: In a Validation activity, the Document field value was not cleared upon form removal and existed across validation activities in different jobs.
1937514, 26638680: When a Data object variable was used in a post-validation handling process map, the job was suspended at extraction with the following error: “Please provide a valid data object variable value.”.
1937505, 26616042: When there were more than 2100 categories, different areas of the TotalAgility Designer reported the following database error if the Category was set to “All”: “The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.”
1936109, 26664873: The backlog of wsa_messages in the Reporting_Staging database logs displayed the following errors: “Index was outside the bounds of the array.” and “The given key was not present in the dictionary”.
1935749, 26660325: In a Validation activity, when the documents were moved to a new subfolder, the user interface sometimes became unresponsive.
1935444, 26663453: In a Document review activity, the drop-down list incorrectly opened the document that the mouse was hovering over, instead of opening the document that was clicked.
1931964, 26640106: The case fragment jobs that were older than the retention period configured on the process maps still existed in the database instead of getting deleted.
1931087, 26652373: In a Validation form, unexpected highlighter sections were added in the table cells when lassoing the values from an image. As more cells were modified, more sections were created which made the image blurred and not readable.
1929060, 26647304: In Capture forms, if the Enable Replay Protection setting was selected using the Configuration Utility, the forms stopped working and an error appeared.
1926963, 26647990: “If the “Merge page PDF data” option was enabled during the PDF generation, the PDF was created with broken text.
1925161, 26640277: In a Validation activity, the browser zoom level or screen resolution affected the visibility of the last document folder. This prevented the usage of vertical scrollbar to navigate down to the last document folder.
1924204, 26580329: When the Toshiba e-Studio Remote TWAIN driver was used to scan documents into a TotalAgility 7.6.0.16 Scan form (using WebCapture Service 11.1.0.453), after the initial scan was completed, the subsequent scans failed
1922336, 26647043: The Process tab for a Scan create new job form disappeared from the Fields panel when a new job was created when changing the default layout. The Fields panel was no longer docked to the panel selected previously.
Fix Pack 1
1936275, 26661370: Document Conversion unable to convert email file types.
1930061, 26650715: When performing extraction in Transformation Designer, the fields that were marked as valid at design time were invalid at runtime.
1927826, 26647797: There was a delay between RetrieveAndSetRootId() call finishing and the ReadFolderData() call starting.
1927819, 26654613: The value of the Data object was null when accessing it in a loop.
1923252, 26619818: During the purge of documents, the performance of “DeleteBatchSessSnapshotFact” Performance was not as expected.
1922388, 26596799: The time spent statistics for documents were inaccurate.
1921533, 26626419: Error when checking if a tenant database was online. For more details, see Additional Information.
1901388, 26635545: Data object access containing null or empty values caused JSON errors.
1900165, 26630442, 26629239: Package deployment error in Azure environment.
1899507, 26632094: Timeout issue with large emails and messages failing to import from MSGraph.
1894977, 26630571: Recognition process soft timeout when testing Advanced zone Locator in Kofax Transformation Designer.
1893344, 26570707, 26623238: Performance issues when accessing the project window in Transformation Designer.
1889663, 26580106: Transformation Designer did not work as expected.
1888082, 26623888: Changing documents fired drop-down Selection Changed actions.
1871502, 26614701: The Microsoft Graph import source displayed the sender’s email address and subject line blank in Message Connector.
1870919, 26612244: Issue inheriting extraction group fields.
1866912, 26617771: Incorrect status color for the Active/Overdue tasks in Service Level Agreement.
1866780, 26618855: Exporting Documents Gives Image Conversion error in Kofax Export Connector XML 8.1.
1866291, 26601364: Using Message Connector with text or Filenet export connector suspends jobs and gives an error.
1795242, 26511204: Applying fix pack to Docker Image incorrectly checked the database version.