PSIcapture 6.0, Patch 15

Summary

The latest version of PSIcapture is now available for public release. If any issues arise during your upgrade, please contact support. To help us make PSIcapture the best product possible, report any issues you find to your sales or support representative, or through our support portal at http://support.psigen.com.

Installation Procedure

Versions 4.6 and BELOW: Please upgrade to 5.1.1.10 BEFORE installing 6.0.

Versions 5.0.0.x to 6.0: Uninstall current version, reinstall using Installation Package. Please contact your support or sales representative for assistance.

Version 6.0.0.x: Update currently installed version using Update Package.

Release Notes

Feature Enhancements

  • In Scripting windows, the Build button now provides an on-screen status when the build is successful or unsuccessful.

Bug Fixes

  • OCR text files are now properly merged along with batch documents and pages when using Batch Restructuring.
  • Fixed an issue where the file extension defined in Custom Single Page File Naming was not being applied to files migrated via Folder Export.
  • Fixed a conflict between data fields that are using both Shared Counters and Increment By values.
  • Fixed an issue where a Capture Profile would not retain Flagging settings for a lookup if a second lookup was saved with no Flagging settings.
  • Fixed an issue that caused the product to remove Flag Record configuration settings between batches.
  • Fixed an issue where the White theme for PSIcapture would lose its window border while another program is active.
  • Fixed an issue where the "Do not create Classification Forms that have no rules" option was not showing in the Classification Form Database Import window.
  • Fixed an issue where the Viewer in the Capture/Import Module would still show a page when the last page was deleted from a document.
  • Fixed an issue where a null reference exception error would occur when trying to Preview a lookup of an empty table from Xero.
  • Managed Metadata columns can now be correctly populated again in the Microsoft SharePoint Direct migration

Related Pages:

There is no content with the specified labels