| |
|---|
3.1.101 | When releasing files to a GlobalSearch Inbox, the original filename is now preserved. Addresses an issue where renaming a GlobalSearch field referenced in a GlobalCapture workflow causes errors when using the Batch Manager and when releasing to a GlobalSearch Archive GlobalForms connection errors during GlobalCapture Validate nodes now log an error message to the process history Improvements to GlobalCapture Server installer
|
3.1.102 | |
3.1.103 | Corrected an issue where page count was not accurately calculated when using the GlobalCapture Scan Station in Cloud environments Allows for workflows to use multiple instances of the CRON Import custom node
|
3.1.104 | Corrected an issue where users can click the “Scan” button multiple times in the GlobalCapture Scan Station, resulting in duplicate GlobalCapture processes Users can now select specific Import nodes when using the GC Scan Station with a workflow that has multiple import nodes
|
3.1.105 | Corrected an issue related to using decimal math with S9 notation Added support for the GlobalCapture and GlobalAction workflow designer to accept “workflowId” as a URL parameter. When used with a valid workflow ID, the designer automatically opens that workflow on page load
|
3.1.106 | Case sensitivity is now ignored when a GlobalCapture workflow references fields from different sources with the same name (e.g. “Total” vs. “TOTAL”) Corrects an issue where data validation mismatching can cause misreads when performing line item extraction via OCR
|
3.1.107 | The Release node now supports file name notation when releasing to GlobalSearch Inboxes Corrected an issue where the Email node would erroneously inject “http://” at the front of email links when using {DOCUMENTLINK} notation Corrected an issue where documents would fail to open in GlobalCapture Validation if they underwent separation and then were released to a GlobalSearch Inbox (but not deleted) Performance improvements for thumbnail generation when bursting documents in GlobalCapture Validation
|
3.1.108 | |
3.1.109-111 | Unused |
3.1.112 (3.1 Minor Update) | Corrected an issue where CTS DC “Run Workflow” action fails if a Process Field associated with that workflow is deleted Allows for migration of GlobalCapture workflows with nested Batch Searches Importing GA processes for deleted workflows no longer throw an error “Object reference not set to an instance of an object” The “Use Existing” option no longer incorrectly shows during Rename GlobalForms conflict Moving a process to a Classify node no longer skips Data Extraction Corrects an issue where OCR sometimes fails to extract data via Template Zones that have an OCR profile set Corrects an issue where List results would be removed and/or duplicated when multiple people are making list changes at the same time Corrects an issue where GlobalCapture errors upon reaching a Validate Node with an automatic approval option if the process contains a Table Field Performance improvements with date field validation in GlobalCapture Validation Corrects an issue where Data Lookup nodes do not respect confidence threshold values of 0 Corrects an issue where Email fields have a confidence of 0 when importing emails via Import File, or via Gmail Import custom node Several other quality-of-life improvements: GlobalCapture Update 3.1.112
|
3.1.113 | Node descriptions now support CRLF in the Batch Manager and GlobalCapture Validation and HTML for processes in Validation status Import Nodes using the “Error Importing” default Batch Search now reference the “Current Node” property by node name, rather than node ID (note this only affects Import nodes created after this update is applied) GlobalCapture Validation now supports field suggestions. This is toggleable as a User Option Corrected an issue where GlobalCapture Validation would not respect hotkey shortcuts (such as ctrl+S, ctrl+D, and ?) GlobalCapture Validation now supports hotkey shortcuts for “Burst” (ctrl+U) and “Burst and Delete” (ctrl+shift+U) actions Corrects an issue where changes to Index Field data do not persist across documents bursted via GlobalCapture Validation Corrects an issue where Dynamic List options do not update when bursting documents in GlobalCapture Validation Corrects an issue where thumbnails do not load for documents bursted via GlobalCapture Validation if the parent process is closed before thumbnails are loaded for the bursted process Corrects an issue where Batch Searches would not return processes for users in a trust domain secured via a group in the primary domain Performance improvements with GlobalAction engine process polling
|
3.1.114 | |
3.1.115 | Unused |
3.1.116 | Condition node now supports multiple conditions, advanced condition logic, and more: Condition Node (GlobalCapture 3.1.116 and up) Added support for referencing more process properties using S9 notation Adds support for “Use Existing” conflict resolution option when importing GlobalCapture workflows that import via a Batch Search that does not match an existing Batch Search in the target environment Corrects an issue where repeated copy/pasting of nodes when designing GlobalCapture workflows may result in a workflow that can be saved, but not opened Corrects an issue where workflows can be saved as Published when there are single-output nodes without links if the node is inside a Group
|
3.1.117 | Adds support for Cisco Duo as a third-party authentication provider Improvements to error logging and node history when releasing documents to a GlobalSearch Archive Corrects an issue where the “Resynchronize GlobalAction” action fails if a GA process exists that references a non-existent GlobalSearch document
|
3.1.118 | |
3.1.119 | Table Field columns can now be referenced by name in addition to Field ID when using S9 notation Ctrl+Shift+X can now be used to clear all Fields, Multi-Value Fields, and Table Field data in GlobalCapture Validation
Deleting a parent process in GC Validation now deletes all existing bursted processes as well Corrects an issue where users are shown all fields when taking the “Save Without Action” action after bursting a document in GC Validation Addresses an issue where using Custom Nodes can sometimes cause the GlobalCapture Engine to use more RAM than intended Corrects an issue where the “Current Node” field is incorrectly set to the previous Validation Action, rather than the Node name GlobalAction now updates the GlobalSearch document’s Lock status when the process is moved to a different workflow via a custom node
|
3.1.120 | Corrects an issue when migrating workflows where Square 9 Group conflicts would appear under “Table Field Conflicts” in the conflicts report Corrects an issue where the GlobalCapture Batch Manager redirects you to an invalid URL “undefined” if you log out of GlobalCapture in a separate tab The Table Field pane now remains open in GC Validation if you move between processes that share the same Table Field Corrects an issue where advanced math notation would not evaluate when reference column names in Table Fields using S9 notation Improvements to load speeds when taking GlobalAction workflow actions from the GlobalSearch Web document viewer in trust domain environments
|
3.1.121 | More improvements to load speeds when taking GlobalAction workflow actions from the GlobalSearch Web document viewer in trust domain environments Corrects an issue where the Condition node was considering only the date and not the time when using {NOW} S9 notation
|
3.1.122-3.1.126 | Unused |
3.1.127 (3.1 Minor Update) | |
3.1.128 | |