Moving You Forward A first look at the New FileBound 6.5.2

Transcription

1 Moving You Forward A first look at the New FileBound An overview of the new features that increase functionality and ease of use including: FileBound Service Pack FileBound Capture 6.6 New Features FileBound Central Installation New Features FileBound Web Parts for SharePoint Integration Platform New Features

2

3 New Features and Functionality FileBound Capture - Improved OCR Speed 1 FileBound Capture - File Summary 1 FileBound Capture - Dockable Line Item and File Summary Panel 2 FileBound Capture - VBScripting Support in Templates 2 FileBound Capture - Multiple Word Support for Pattern Matching 3 FileBound Capture - Rename Page in Tree-View 3 FileBound SharePoint Web Parts - Assigned Documents 4 FileBound SharePoint Web Parts - Project Selection 4 FileBound SharePoint Web Parts - Integrated Search 5 FileBound Central Installation - Register On-Demand Sites 6 FileBound Central Installation - Install Site as Default, New, Virtual 6 FileBound Central Installation - Site Health Check 7 FileBound Central Installation - Install Using Existing Database 8 FileBound Central Installation - FileBound Drive with Upgrade 8 FileBound Central Installation - Set Default Website Culture 9 FileBound Central Installation - Updated User Interface 9 FileBound Central Installation - Select Previous Versions 10 FileBound Central Installation - MS Server 2012 Support 10 Integration Platform - Map E-form and Extra Data for Export 11 Integration Platform - Connection Error Notifications 11 Integration Platform - Workflow Action for Failures 12 Integration Platform - Error Log Document Creation in File 13 QuickBooks Connector - QuickBooks File Selection 13 QuickBooks Connector - QuickBooks 2010 and 2013 support 13 Microsoft SQL - Trim Data on Import 14 Microsoft SQL - SQL Views Support 14 On-Demand Dashboard Enhancement - Automation Event Statistics 15 FileBound Release Notes (Issues Resolved) 16 FileBound Release Notes (Issues Resolved) 17 FileBound Release Notes (Issues Resolved) 17 FileBound Release Notes (Issues Resolved) 18 FileBound Capture 6.6 Release Notes (Issues Resolved) 19 FileBound Integration Platform 6.1 Release Notes (Issues Resolved) 19

4 FileBound Capture - Improved OCR Speed FileBound Capture utilizes Optical Character Recognition (OCR) for index and document templating processes and click indexing. OCR speed has been improved by adding support for dual-core processors. The time between scanning, or importing, and when the templating process completes can be cut in half if using a dual-core or greater processor. This allows for double the number of documents to be processed in the same amount of time. A FileBound Capture user that is currently scanning invoices on a PC that has a quad-core processor and has a library of 20 templates will experience a decrease in the amount of time that it takes to capture and template the documents. This user will notice that is takes 50% less time to complete the process. FileBound Capture - File Summary An indexing window that allows a user access to all of the index values for the files in the batch. This window allows a user to enter or edit index information for the files in the batch. When templates are used, clicking the index information in the File Summary Screen will display the zone on the document that the data was extracted from. Provides a grid view of all the index information for the files in the batch. From here a user is able to perform index value Quality Assurance review and make any changes or additions. This can be beneficial when utilizing templates during the indexing process to confirm the data was captured correctly without having to page down through each page and file in the tree-view. Applications for a summer intern program are being scanned and a template has been created to extract information to be used for index fields. After capture and templating a user can view the File Summary screen and verify the captured content. If an issue is found the user is able to click the index field and the location on the document where the template was looking for data will be displayed. This allows the user the ability to quickly manually fix the data Get Certified at:

5 Moving You Forward A first look at the New FileBound FileBound Capture - Dockable Line Item and File Summary Panel When enabled, the Line Item Indexing and File Summary panels appear at the bottom of the Capture window. This panel is able to be docked on the right side and bottom of the screen as well as on the left as a floating window. Being able to dock this panel on the right-side of the screen, or left as a floating window, allows a user to view as much vertical content of a normal scanned paged as possible. The panel is not using extra screen space at the bottom of the document that could be used for viewing document content and not forcing the user to scroll down on the document. Users are entering Line Item detail for scanned invoices. The monitor that the user is using does not have a large resolution, but the user does have two monitors. The user is able to move the panel at the bottom of the application window and peel it away from the bottom and make it a floating window. Now the Line Items entry panel can be displayed on the second monitor and the invoice is displayed on the first monitor. FileBound Capture - VBScripting Support in Templates VBScripting can be applied to a value that is extracted from a document during the templating process. By allowing VBScripting to be applied at the time that an index value is extracted by a template the data can be formatted to meet possible indexing criteria using common VBScript functions. This provides the ability for a script to be used determine the extracted value and return a different value to be used by the index field. New car purchases are being scanned and templated. The VIN number for the car is captured using a template. Only the last 8 digits of the VIN need to be used to identify the car in an index field. Using the VBScript the last 8 digits of the VIN can be extracted and used for the index field instead of the entire VIN number. Learn more at:

6 FileBound Capture - Multiple Word Support for Pattern Matching When using pattern matching within a template the pattern match will now support looking for more than a single word, or term, in the pattern. The desired pattern that a template looks for may be a string of more than just one word. This allows users to configure the template to use a regular expression pattern match to find all of the desired words to be used for indexing. Invoices are being scanned at different locations with different scanners. To eliminate concerns about users changing dpi settings a pattern match can be used to extract a Vendor Name from the top left corner of an invoice. Using the Pattern Match field type the template can look for the vendor name that consists of 3 words MGI Sporting Goods, for example. FileBound Capture - Rename Page in Tree-View While indexing in FileBound Capture users have the ability to rename a page within the tree-view list of the Files and Documents. When users are using custom page names they are able to apply those name changes at the time of capture before it is uploaded to FileBound. A FileBound project is being used to store contracts. The file containing the contract has a divider that is labeled contract that will contain the contract. There is also a divider that is labeled Support Documents. When each of these different documents are scanned within FileBound Capture the page name of the document is changed to indicate the name of the document before it is uploaded Get Certified at:

7 Moving You Forward A first look at the New FileBound FileBound SharePoint Web Parts - Assigned Documents Provides a SharePoint user the ability to view documents that have been assigned to them within FileBound. Users that perform daily work inside of SharePoint have access to see any documents that have been routed to them in a FileBound workflow process without having to log into FileBound. From within SharePoint the user is able to click the view button to view the routed document and associated pages within a FileBound Viewer. From here the user is able to take action on the routed document. A company uses SharePoint as a company intranet portal for all company communication. It is a central point for all company users to find information and work that they need to complete for the day. Within this portal they are able to view and directly access documents that have been assigned to them to take action on without having to separately log into FileBound. FileBound SharePoint Web Parts - Project Selection Provides a SharePoint user the ability to select a project to search and work in within FileBound. A user has an easily accessible menu of documents that is available to them within SharePoint. When the user clicks on the Project name they are taken directly into FileBound and they are able to search, view and work with any documents that they have been granted access to. A company uses SharePoint as a company intranet portal for all company communication and interaction. The company uses FileBound store all documents. A user can click on the project name to access the type of documents that they need to view without the need to leave SharePoint and open FileBound. Learn more at:

8 FileBound SharePoint Web Parts - Integrated Search Integrates the SharePoint search with FileBound. When a user performs a search the results will contain information that matches within SharePoint and within FileBound. SharePoint users are able to perform a single search that will search both SharePoint and FileBound at the same time using the search criteria that was entered within the Search box in SharePoint. The search results will separate the content that was found in SharePoint and the content that was found in FileBound in two different sections in the search results. SharePoint has been configured to store information about customers. Documentation related to these customers is stored within FileBound. A user enters a customer number into the Search box within SharePoint and performs a search. Information that is stored in SharePoint and information about the documents for that customer in FileBound are both returned and displayed in the search results. When the user clicks on a search result from FileBound they are taken to that information without having to log out of SharePoint and accessing FileBound to perform the search again to find the content Get Certified at:

9 Moving You Forward A first look at the New FileBound FileBound Central Installation - Register On-Demand Sites A FileBound On-Demand site can be registered with Central Installation. This will display the site within the Central Installation window and allow easy access to the Central Administration window for the site. Resellers are able to register all of the different FileBound On-Demand sites for their customers. This provides a central location for them to be able to access the Central Administration window for each site and perform any configuration changes or additions that need to be made. A reseller manages 10 On-Demand sites for different customers, they create users and groups, build projects, and monitor automation server utilization as part of their management of the sites. The reseller is able to install FileBound Central Installation on a workstation in their office and register all 10 sites. Using this application they are able to directly access the Central Administration window for any of the sites and quickly perform their tasks. FileBound Central Installation - Install Site as Default, New, Virtual When installing a FileBound site a user is able to designate if the site should be installed as the Default Website for the server, a Virtual Website on the server, or as a new Website. Provides the system administrator flexibility in where the FileBound site will be hosted on the Windows server. If it is desired to have the FileBound website as the default website on the server the admin does not have to perform a manual installation of the FileBound website. This allows for upgrades and other maintenance to be performed using FileBound Central Installation in the future. A new FileBound system is being installed that will only be available on an internal network. The FileBound site administrator wants users to be able to access the site using: and not During the installation process using Central Installation the FileBound site can be selected to be installed as the default website on the server hosting the FileBound website. Learn more at:

10 FileBound Central Installation - Site Health Check A FileBound Site Health Check will determine the health and performance level of a FileBound system. This includes checking key FileBound database tables and functions, CPU resources and memory utilization. A FileBound site administrator is able to access a report that will display if these items are within acceptable limits. FileBound site administrators are able to monitor the health of their FileBound database and web server utilization without the need to log into these servers. The FileBound site administrator does not have to rely on an IT employee to run queries on the FileBound database or review web server memory and processor utilization. A FileBound site administrator is a FileBound system administrator but does not have network or account access to be able to access the FileBound database or web server that is hosting the FileBound website. The FileBound site administrator may notice that their site is starting to run slow. The administrator is able to use FileBound Central Installation to run the Health Check that will evaluate performance of the FileBound database and web server process or and memory utilization. The check will alert the user if the key functions and processes of the database and web server fall within acceptable limits without having to run queries on the servers. The Database Fragmentation check may indicate that it does not fall within acceptable limits. Now the FileBound site administrator is able to contact the FileBound database administrator and alert them to a possible issue for further investigation Get Certified at:

11 Moving You Forward A first look at the New FileBound FileBound Central Installation - Install Using Existing Database FileBound Central Installation can be installed and used to install a new FileBound website and use an existing database. During the installation process the existing database will be upgraded to the version of FileBound that is being installed. This allows for existing FileBound websites to be upgraded to start using FileBound Central Installation with new website code but use an existing FileBound database from an previous version. A long time FileBound customer wants to upgrade to the latest version of FileBound and start using FileBound Central installation to manage the site. The customer has purchased new hardware to host the FileBound website and plans to start with a new installation of the FileBound website but use their existing FileBound database. FileBound Central Installation will allow them to install the new FileBound website and use the existing FileBound database, and automatically upgrade the database to the current version during the installation process. FileBound Central Installation - FileBound Drive with Upgrade FileBound Central Installation will install and configure FileBound Drive on an existing FileBound site that has been upgraded to FileBound version 6.5.x. FileBound Drive is able to be added during an upgrade to a site that was previously on a version older than FileBound 6.5. An existing FileBound customer use FileBound Central Installation to perform an upgrade. Their site is configured to Secure Socket Layer (SSL). After the upgrade they will be able to configure their FileBound site to utilize FileBound Drive to access content. Learn more at:

12 FileBound Central Installation - Set Default Website Culture Using FileBound Central Installation a system administrator is able to set the culture that the FileBound system will be used in. This will allow for proper date formats for the country or region that the FileBound system is being used in. When a FileBound system is implemented in countries that use a different date format than the Middle-endian format commonly used in the United States a FileBound site administrator is able to set this using FileBound Central Installation. The administrator does not have to manually make this change within the FileBound database. A FileBound system that is installed in Paris, France will need to use Little-endian date format of Day/Month/Year. Using FileBound Central Installation will allow the FileBound administrator to be able to specify the culture setting that will provide proper date formats during the installation process. FileBound Central Installation - Updated User Interface The FileBound Central Installation interface has been enhanced and streamlined to help guide users in the setup and maintenance of a FileBound server. The interface has been optimized for clarity and consistency between the different screens of FileBound Central Installation to allow users to easily configure their FileBound installation Get Certified at:

13 Moving You Forward A first look at the New FileBound FileBound Central Installation - Select Previous Versions When using FileBound Central Installation to perform a new installation of a FileBound server, a user is able to select from the current version or from previously released versions of the FileBound server. FileBound Central installation is able to install previously released versions of FileBound and not just the most current release. This allows FileBound site administrators that desire to run a version behind the most currently released version or later to be able to benefit from all the functionality provided by FileBound Central Installation and not be forced to run the latest version. The IT Director for a company has implemented a company policy that they will not install the latest version of any software. The software must be 1 full version behind the latest version, or at least on the third service pack release on the current version. FileBound Central Installation will allow the user to select from previous versions of which they want to install during the installation process. FileBound Central Installation - MS Server 2012 Support FileBound Central Installation supports installing a FileBound server on server running a Microsoft Server 2012 operating system. A FileBound system is able to be hosted on the latest version of Microsoft Windows Server. Learn more at:

14 Integration Platform - Map E-form and Extra Data for Export Connectors that export data have the ability to export data that is stored within E-form Data and Extra Data for the file or document that is being exported. If the data that is being exported was created using an e-form any data that is not stored within an index field can also be exported. A job application has been filled out online and submitted to a FileBound system to be routed for review and hiring approval. The application contains many different fields of information and not all of the information has been mapped to index fields. When the application is approved and the employee is hired, the submitted data, index fields, e-form data and extra data, can be exported to be made available for automatic import into the company s HR software. Integration Platform - Connection Error Notifications If the Integration Platform is unable to make a connection to the source that it will import data from, or export data to, an notification can be sent to a specified address. The message will contain information about the error that has occurred. When the Integration Platform is unable to connect to a data source an administrator of the integration is able to be notified that an error has occurred. This allows the administrator to be proactive and investigate the cause of the error and correct the situation in a timely manner. If the notification is not enabled the error could possibly go undetected and users will be unsuccessful in finding content that should have been processed. Customer order data is being exported from FileBound and imported into a SQL server based CRM on a nightly basis using the Integration Platform and the SQL connector. Users will work in the CRM and be able to view information about customer orders. If the Integration Platform is unable to establish a connection to the SQL server an alert with the error message can be automatically sent to an administrator to correct the issue and start the import Get Certified at:

15 Moving You Forward A first look at the New FileBound Integration Platform - Workflow Action for Failures If the Integration Platform encounters an error while exporting data the document that initiated the export can be routed to a unique step within the workflow. This will alert users that an error has occurred. When configuring the export, users are able to select the step in the workflow process that the document will be routed to when the error occurs. When the Integration Platform is unable to export data because of any reason, such as a data type mismatch, the document that initiated the export can be routed to a different step in the workflow that is expressly intended to handle errors that occur during export. This workflow step can then be configured to notify the appropriate people with an appropriate message. Invoice data has been entered and a PO number has been capture and entered but a zero has been mistaken for the letter O. When the data is exported into the account system, the account system is configured that the PO number is a numeric type of data. When the Integration Platform tries to export the data the export fails because of the alpha character in the PO number. In this situation the invoice will be routed to the designated step for failed exports. Learn more at:

16 Integration Platform - Error Log Document Creation in File If an error occurs during the export of data a text document can be created that will contain information about the error. This document will be saved to a specified divider within the file that contained the document that initiated the export of the data. When the Integration Platform is unable to export data because of any reason, such as a data type mismatch, an error message is created. Storing this error message in a text document within the same file as the routed document in FileBound allows people other than a server administrator to evaluate the cause of the error. This error is also written into the application error log but to view this error log a user must have access to the server that is running the Integration Platform. Normally this a server administrator within an IT department. Invoice data has been entered and a PO number has been captured and entered but a zero has been mistaken for the letter O. When the data is exported into the account system, the account system is configured that the PO number is a numeric type of data. When the Integration Platform tries to export the data the export fails because of the alpha character in the PO number. In this situation a text document will be saved to the specified divider within the file containing the routed document. The text file will contain the error message stating that there was a data type mismatch. At this point the user is able to correct the PO number and send the invoice back to the export step. There is no need to access the server log to determine why the export failed. QuickBooks Connector - QuickBooks File Selection When configuring the QuickBooks connector within the Integration Platform the QuickBooks user is able to select the QuickBooks file to be used for the integration. If an organization has more than one company setup with QuickBooks a user is able to select which company the integration will connect to. QuickBooks Connector - QuickBooks 2010 and 2013 support The QuickBooks connector has been upgraded to support QuickBooks Get Certified at:

17 Moving You Forward A first look at the New FileBound Microsoft SQL - Trim Data on Import Imported data will have blank spaces at the beginning or end of the imported data removed. When importing data from another system the data may contain unwanted blank spaces at the end or beginning of the data. Leaving these blank spaces my cause issues when searching or using the data within value checks in workflow. Purchase Order information is imported from an accounting system into FileBound using the Integration Platform and SQL connector. When the Purchase Orders are scanned using FileBound Capture only the PO number is indexed and then uploaded, during the upload to FileBound the PO s will be merged into the existing files using the PO Number. When the original PO data is imported the PO number contains a blank space at the beginning, if this is not trimmed during the import using the Integration Platform the scanned PO will not merge correctly. Microsoft SQL - SQL Views Support During the import of data from a SQL Server to a FileBound system the Integration Platform can be configured to pull the data from a View within SQL and not just a single database table. When importing data from a SQL server the data being imported may not reside in a single table, but may be comprised from several different tables in the database and organized in a single SQL view. The Integration Platform is being used to import information about loan applications into FileBound. Then when the application is scanned into the FileBound the file information will already exist in FileBound and reduce the amount of indexing that is required. The information that needs to be imported is stored in three different tables within the SQL database. A View has been created in SQL to organize all the necessary information. The Integration Platform is configured to access the view and retrieve the necessary information. Learn more at:

18 On-Demand Dashboard Enhancement Automation Event Statistics The On-Demand Dashboard in the FileBound Partner Portal has been enhanced with new Automation Event Statistics. Statistics for your On-Demand customers will now display information about the automation events that have been processed in the past 24 hours, the events waiting to be processed and any errors that have occurred in the past 24 hours. As a reseller you are able to monitor the events that are occurring for your customers and identify any possible bottlenecks in event processing. If errors do occur you are able to view the errors and help solve any issue that might be causing the error. An On-Demand customer is using a FileBound Folder Import Process and an Auto-OCR process. As their reseller you are able to login daily and verify that their automation processes are occurring. You may notice that the folder imports are constantly waiting to be processed. Seeing this you are able to recommend that maybe another instance of the FileBound Enterprise service needs to be configured to run for the site to prevent this consistent backlog Get Certified at:

19 Moving You Forward A first look at the New FileBound FileBound Release Notes (Issues Resolved) Help link on the Welcome page after an initial install will now open the help system correctly. When viewing the Workflow Status Report using Internet Explorer 8 the column headings are now properly aligned with the column data. E-form Process step can now be added without causing an Exception Error when using a new database that does not have any Workflow Processes. Child Process step can now be added without causing an Error when using a new database that does not have any Workflow Processes. Save and Add Another will now remember the field data when the Remember Fields check box is selected when using Google Chrome. Clicking in the document viewer tree-view with the Show All Separators/Dividers option selected will no longer produce an Object Reference error message. Documents saved from the Indexing Queue that are set to automatically route into a Workflow Process will now properly route if the first step of the process uses a Decision stencil to evaluate the Separator or Divider of the document. $$UserName$$ is now working as expected within Workflow Processes. Stamps are now listed in the correct location within the Web Viewer. Workflow Status Report now properly displays results when they contain information about a user that has been deleted. Users can no longer from the Report Viewer if they do not have the proper rights. 1/1/1990 is no longer displayed as the Last View Date on the File Details page when a document has not been viewed. The Unindexed Queue option has been removed from the Windows Viewer. When configuring an e-form the Detail Form can now be unselected if it has been previously selected. Landscape oriented images will now fill the entire page when printed from the Windows Viewer. E-form Data is now available when a document is moved through automated steps in a workflow process. Line Item Detail Panel now properly saves data if the viewer is closed before clicking the Save data button. Documents are now properly uploaded from the File Entry page when the divider name contains an ampersand symbol (&). The Web Viewer will now sort and display Files in the same order as the Search Results grid. Access Administrator users are now able to run the User Login Report. If set, a document is now automatically started in a Workflow Process when uploaded from the Add Content page. Visual Assignments widget is now properly displaying e-forms. Hidden users are no longer displayed in the list of users to add files to their clipboard. Users can remove signatures within the Web Viewer. Documents can now be routed in the Web Viewer without having the tree-view nodes expanded.»» Searching for a file within the Indexing Queue will now populate all index fields to allow the document to be merged with an existing file. Learn more at:

20 FileBound Release Notes (Issues Resolved) User Stamps are no longer added to the Global Stamps. Using the Cancel and Start in New Process option for documents on a Multi-All workflow step type will now perform this action for all documents on the step and not display an error message. $$USER.FULLNAME$$ is now correctly entering the User s Full Name when used on a HTML e-form. Required index fields are now able to be updated using the batch update functionality in the clipboard. Blank rows in the Line Item Indexing panel are no longer created and saved if the row does not contain any data. MS Word and MS Excel documents are now uploading and saving properly when uploaded as attachments to an external HTML e-form submission. Master Sheets are now merging correctly when multiple files are merged together. Various FileBound Touch issues have been fixed. FileBound Release Notes (Issues Resolved) Fixed memory spike issue when loading the Indexing Queue that contained multiple PDF documents that displayed the file type icon. Multiple documents can now be exported, ed, and printed from the Web viewer when they are selected using the Multi-selection check boxes. When navigating between files in a document viewer the any project link type fields will now refresh properly. Files that use two project link type fields will now properly update within the Windows viewer File Details pane. The Windows viewer will now properly release memory when the viewer is closed. FileBound Release Notes (Issues Resolved) Fixed issue that prevented users from adding line items if the line item key field value contained the quote ( ) character. Recycle Bin is now properly displaying all records. Tasks can now be completed correctly from the Visual Assignments Workspace Widget. The Move to New File Option in the Windows Viewer is now working correctly. Multi-page.tiff images uploaded to a specific project in the Indexing Queue using Drive no longer sets the project to Global. The page count is now set correctly when uploading a single page.tif to the Indexing Queue using Drive. Fixed issue that prevented parent level workflow processes from being selected in areas such as project level routing and the scheduled workflow process configuration. Renditions are now being stored in proper alternate location when an alternate storage location is specified. Fixed issue with e-form data and extra data variables not being evaluated or displayed properly when used in workflow process logic. Workflow processes that utilize a high number of connections (9 or more) no longer causes the workflow process to error and not complete. Systems that utilize Active Directory and remote document storage locations no longer receive a Path Denied error message when adding content using the Add Content screen Get Certified at:

21 Moving You Forward A first look at the New FileBound FileBound Release Notes (Issues Resolved) Folders and Documents that use a period (.) in the name now display properly within FileBound Drive. When canceling documents on a Multi-All step within the Central Administration window an error stating Cannot Find Object ID XX is no longer displayed. Fixed an issue with large amounts of OCR data when using the Site-OCR process on messages with embedded images. FileBound Drive now works correctly when using Active Directory for authentication into FileBound. When exporting double-spaces are no longer truncated to a single space. Web Viewer now properly hides annotations when using the Hide Annotation Layer button. Files will now properly merge when a date field is left blank. Quotes in Workflow comments no longer cause display issues with the Workflow Status Report. Back slashes and forward slashes in a page name no longer cause display issues with the File Details screen. When deleting a Workflow Process in the Central Administration window the list of processes will now properly refresh the list. When requesting a file you are now able to properly change the request date. File Details screen now displays a page name even if it has not been changed from the default of Page 000x. Improved Recycle Bin loading time when it contains 10,000 or more items. Multi-page tif files that are uploaded using FileBound Drive are now properly split into single page.tifs. Importing a Multi-page PDF into the template setup will now properly display all the pages Barcodes printed from the File Details screen now print in proper order if the display order has been changed. Viewing a PDF e-form in the Web Viewer no longer updates the Date Filed but instead updates the Last View Date. Improved Viewer speed when using a Project Link index field that is linked to a project with a large number of files. Fixed an issue with the Child Process workflow stencil that would not properly complete workflow steps. The Archive Name is now displayed properly within the Web Viewer. When logging into FileBound using Internet Explorer the Enter key is now functioning properly. Double Quotes in Workflow comments no longer cause display issues with the Workflow Status Report. Workflow steps are now properly loaded when editing the Visible Queue widget for the first time. Fixed various issues with widgets on the Workspace with different browser versions. Web Viewer now displays dividers in proper descending order. Fixed issue that did not properly assign a due date to all users when using an Assignable step in workflow. Windows Viewer will now load properly when viewer icon is clicked in the document list on the File Details screen. Learn more at:

22 FileBound Capture 6.6 Release Notes (Issues Resolved) Converting Page(s) to a Template no longer causes an error message to be displayed. Barcode Same Page option no longer removes the first page. Invalid date formats are no longer allowed in a Date type of field. Option list searches no longer are performed like a wildcard search. Custom Regular Expressions now export and import correctly. Errors no longer occur when performing an upload when the first index field contains /. After syncing templates with a server the Location column in the Template list properly displays Local instead of Server. Project Lookup button now available for Option List and Project Link field types. Batch Lookups no longer display an Unhandled Exception Error. FileBound Integration Platform 6.1 Release Notes (Issues Resolved) Documents are no longer sent automatically to the step created immediately after the exporting step, they will go to the selected step. The parent workflow process name can now be selected, this will allow the Integration Platform to use the latest published workflow process during the export. During import any fields that are not mapped will no longer be automatically cleared Get Certified at:

23 Moving You Forward A first look at the New FileBound Learn more at: