| Table of Contents | ||
|---|---|---|
|
Use the Release Node to release data and documents from a Workflow to GlobalSearch or to the file system. You can use multiple Release Nodes in a Workflow if you need to release to more than one location or if you need to conditionally release to different locations based on previous workflow steps.
Node Properties
Title
Add a title for this node. Titles are useful when reading the history in the history of a workflow for easier understanding of the overall process.
Description
Provide a synopsis of what this node is doing, or make note of any important details. This is useful for providing additional information such as workflow details and use case information. A good description is helpful when returning to modify the workflow in the future.
Release Types
Release to File
| Note |
|---|
Release to File is available for GlobalCapture on-premise solutions only. |
You can release documents from the Workflow directly to a local or network file system.
Export Path: The location of the file folder to release document to.
| Info |
|---|
If releasing to a network share, be sure to use a network addressable path (UNC path), never a mapped drive. Also be sure that the service account GlobalCapture is using has permissions to the network share. |
| Excerpt | ||
|---|---|---|
| ||
File Naming Format: When specifying the File Naming Format, you can specify a specific value or use Square 9 Notation to set the values automatically.
|
Overwrite Existing Files: Overwrite files in the release folder with new files of the same name.
| Excerpt | ||||||
|---|---|---|---|---|---|---|
| ||||||
Delete Files After Release: Remove the file from the GlobalCapture working directory. If releasing to multiple locations, this should only be enabled on the final release node.
|
Release to Archive
You can release your GlobalCapture data and documents directly to an GlobalSearch Archive.
Select the Square9API Portal, Database, and Archive.
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Import to automatically generated child archive: Create a destination archive based on the selected process field data. When enabled, select the name of the archive from the Process Field Value for Archive Name list.
| Warning |
|---|
Exercise caution when using this feature.
|
Release to Inbox
You can also release to Inboxes in the GlobalSearch. Documents are most commonly released to an Inbox post-processing , where no indexing has been automated but where features like page separation or image enhancement are required. You then access the documents from the Inbox, where they can be indexed into an Archive manually.
| Note |
|---|
Index Field data is not retained in an Inbox. If you have extracted data (from using the Process Field Node, or the Validation Station, for instance) it will not be retained in the Inbox. Release to an Archive insteadto preserve associated data. |
When selected, you’ll be asked to choose an Square9API Portal, Database, and Inbox.
| Insert excerpt | |||||
|---|---|---|---|---|---|
|
|
Check Network Share Permissions. If releasing over a network share, the user running the GlobalCapture service needs to be a user with rights to the designated export directory.
File Naming Format: When specifying the File Naming Format, you can specify a specific value, or use Square 9 Notations* to set the values automatically.
| Info |
|---|
*For more information on Square 9 Notations, please refer to our knowledge base article, “S9 Notations”. |
| Tip | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Using S9 Notation for the File Naming Format
|
Use Cases
Configure multiple release nodes to release to different locations
In this example, I've filled out three different release nodes all configured to different archives within GlobalSearch. Having multiple release nodes is useful for automatically routing documents, without the need for users to move them manually into their proper locations.
Configure consecutive Release nodes to export to multiple locations
In this example, I've created a GlobalCapture workflow that utilizes an Approve or Denied decision to route documents to their proper locations. When a document has been denied, the first release node is configured to save a copy of the document locally to a file folder and the second to an Inbox in GlobalSearch. To do this, I will need to uncheck the option to delete files after release on the first release node so a document exists to be released by the second release node.
This process is useful to save copies of the document before they go through the remainder of the workflow, or to be used for other purposes without losing the original copy of the document.
Configure multiple release nodes to save copies of documents
In this example, I've created a GlobalCapture workflow that utilizes multiple release nodes at different steps throughout the workflow process. immediately after importing a document, we can add in a release node to save the original document before it proceeds through the workflow process by disabling delete files after release.
Adding in release nodes after certain steps can be useful for testing new functionality in workflow processes, so that we can visually see what's happening to the document throughout the process. This could be used before performing PDF conversion, or OCR Extraction, even deleting and separation actions as well.
| Tip |
|---|
Release to Multiple Instances of GlobalSearchIt is possible to have a single capture instance which is releasing to multiple GlobalSearch instances. If you run a service bureau, for example, you can capture documents and then release them to various customer GlobalSearch instances. You will be able to define the end points for each of those customers in your service bureau capture process. |
| Tip |
|---|
Release to Nested ArchivesSuppose that you want to release to the PO Archive, with your purchase orders organized by vendor names. You can release to Sub-Archives under PO Archives based on vendor names by enabling the Import to Automatically Generate Child Archive setting and then select the Vendor Name Field in the Process Field Value for Archive Name list. That way, if a Sub-Archive for a vendor doesn’t already exist, one will be automatically created. Just be careful when you use this, because those new Sub-Archives are not automatically added to your existing Searches. You will need to manually create the Searches, if you ever want to find the documents in those Sub-Archives. |
Important Notes
| Info |
|---|
Release PerformanceFor "on premise" customers (customers who host their own GlobalSearch environment on the same network as their GlobalCapture environment), performance optimizations can be made to minimize network traffic related to file transfer at release time. In the Square9.GlobalCapture.exe.config (by default, C:\GetSmart\CaptureServices\GlobalCapture_1) add the following entry to the appSettings section of the file: When this key is present in your environment, files are transferred directly in the file system, rather than through API routes. This results in faster transfer rates as files don't need to be broken down into chunks, transferred, and then reassembled. All customers where throughput is a consideration should leverage this setting. |
| Info |
|---|
Field Caching (GlobalCapture 2.1 and earlier)GlobalCapture systems that release to GlobalSearch (on-premise or in the cloud - C2) have the ability to cache GlobalSearch field details. This minimizes network traffic and improves processing speeds. All new installations from GlobalCapture 2.2 and greater will have caching settings enabled by default. Customers upgrading from a previous version may not have the settings present. Any customer using GlobalSearch with their capture applications should add this setting. In the Square9.GlobalCapture.exe.config (by default, C:\GetSmart\CaptureServices\GlobalCapture_1) add the following entry to the appSettings section of the file: <add key="FieldTimeout" value="600"/> |