...
Legacy “GlobalSearch Capture Workflow” customers will not have access to historical batch history when upgrading to this version. Customers upgrading from versions of GlobalSearch that included Capture Workflow will not see this data in the updated interface. Customers using Square 9’s XML Import utility should note that legacy actions from this utility are logged here as well, and will also no longer be available. Any errors in the XML Import process will continue to log to the configured file system as always.
For new installations, legacy demo workflows are no longer deployed. Please use the Square 9 SDN to access the latest most comprehensive workflows available for production deployments.
Customers leveraging Frevvo specific functionality should make sure workflows are updated to remove those connections. Frevvo nodes and references in Square 9 products are completely deprecated in this release.
Legacy “GlobalSearch Capture Workflow” customers will not be able to directly install/update to version 3 if they do not wish to rebuild their workflows. Customers on such legacy versions will need to upgrade to an intermediate version before migrating to version 3 if they wish to keep workflows. These customers are strongly encouraged to speak to your Square 9 representative about options prior to upgrading.
GlobalAction customers using GlobalSearch v4.3.1 or below can not directly upgrade their workflows. Customers on such legacy versions will need to upgrade to an intermediate version before migrating to version 3 if they wish to keep workflows. These customers are strongly encouraged to speak to your Square 9 representative about options prior to upgrading.
Customers deploying multiple remote Engines should note connectivity to MongoDB is now performed exclusively through the System and Process portals configuration in GlobalAction Administration. Paths to MongoDB defined here must be accessible to the remote engines. Loopback addresses will not work and will need to be updated to be network accessible.
When configuring barcode recognition in templates, the designer does not NEED to select a barcode, but selecting a barcode type is recommend for performance reasons.
Batch management for Capture and Action are now unified in a common interface. When navigating to the Batch Manager, users with see their default search, regardless of how they linked into the product. Users who wish to always see Action batches can set a default search accordingly, or make sure any links are targeting a specific search ID that meets the user’s intended need.
Communication between Search and Action has been improved. A new option is available on the Admin page for any GlobalSearch portal for re-syncing the state between applications.
When upgrading from older environments where GlobalAction was part of the GlobalSearch deployment, the GlobalAction Engine install will not trigger automatically and will need to be run manually. Alternately, upgrade to a intermediate version before upgrading to 3.0.