Posts

Showing posts from 2015

AutoStore: Excel Data in a Konica Minolta Database Lookup Field

Sometimes, a simple data source can be quite appropriate to supply list items for a user to choose from. In this post, we'll connect a Konica Minolta Database Lookup field to a Microsoft Excel file to serve that purpose. A recent AutoStore project involved the Konica Minolta Open API capture with route to an existing Windows folder structure. After mapping out the basics during the discovery phase, we were looking at basic entries on the touch screen. Client Name Document Type Document Date Based on the selected AutoStore form, the Document Types would vary. Enough was known about the scanning workflows to start building an initial configuration, but the customer still needed to compile a list of the Document Types. Of course, it's simple to add list items into the properties of a List Field, but it means the CFG needs to be edited, saved, and the AutoStore service restarted for the new list to take effect. Relatively speaking, this would be easy for an Auto

AutoStore: AutoCapture Folder Browse

Image
If you're looking for an AutoCapture script to browse folders, then this post is for you. It uses a String List field to provide the folder navigation, as there isn't a tree field available in AutoCapture. To get started, prepare an AutoStore configuration using the AutoCapture and Send to Folder components. Open the AutoCapture component, and add a new Form. Then ... Add a new field. We'll use Folder for the field Name . Set the Type  option to String list . Make the field Required . Enable the Run script on field change setting. Enable the Run on form load setting. Click the [...] button to open the script editor. Now, onto the script. Here's the short-list of what it does: In the script, define the starting folder. Move into a folder by selecting the item. With a folder selected, the list is refreshed with any of its subfolders. Navigate Back, and the list is refreshed with those folders. Stops Back navigation once arrived the start path.

AutoStore: AutoCapture Validate Regex

Image
It is possible to check the field input of an AutoCapture form as it is submitted. In the following example, we begin with an AutoCapture form String  (text) field named "Email To". Make sure the Run on form validate option is enabled. Doing so will execute the Form_OnValidate event handler. Here, we can pass the field value with a regular expression pattern into a custom function named IsValidRegExp() , which returns a True or False. AutoCapture Form Validate RegEx Example '================================================================================ ' CONSTANTS SECTION '-------------------------------------------------------------------------------- Const  REGEX_PATTERN = "^\S+@\S+$" Const FIELD_TO_TEST = "Email To" '================================================================================ ' EVENT PROCEDURES '-------------------------------------------------------------------------------- Function Fo

AutoStore: Processing Date Values

Simply put, dates represent fundamental pieces of document metadata. In this article, we'll look at processing date values with the VB/JScript process component in AutoStore. To illustrate why this can be useful, consider the following scenario. A document needs to be routed to a folder. One of the folders in the destination path is characterized by the year. In the capture form, an entire date value is collected, but only its year is needed for that subfolder. Would we ask the user to input only the year separately? Of course, why should we? We already have the desired date. The year  would just needs to be extracted. Perhaps we already have a mechanism to get what we need. To know for sure, it's important to understand what that date  actually represents. For example: Capture Date Many AutoStore components offer valuable date parts in the Available RRTs list. Their respective values reflect the current date or time. However, not all components provide these RRTs, w

AutoStore: AutoCapture Folder Name List

Image
Can an AutoCapture list field be loaded with the folder names located in a particular directory? The short answer is absolutely, and in this post, we'll look at a simple example which does just that. Where a folder lookup can be useful is when the name of the subfolder represents an entity within its parent folder, and a fresh list is needed to complete the destination path. To illustrate, let's begin by examining a Vendors folder that contains subfolders representing different vendors. Shared Drive Accounting Vendors Vendor A Vendor B Vendor C Vendor D The Vendor names could be manually added to an AutoCapture String list field, or also added dynamically using a form script. We'll examine a couple of touch points: Loading the list field Default a blank list item We'll begin by building a new configuration using the AutoCapture capture component, and the Send to Folder route component. Create an AutoCapture form, and add a new String L

AutoStore: Data Filter Reformat Date

Image
AutoStore can reformat a date during runtime without a process script by using the Data Filter process component. Every day around the world, millions of people save files with a file name. A task so common, so routine, it's easy to forget that certain characters can be problematic. Here is some additional information on this topic from a Windows perspective: Naming Files, Paths, and Namespaces https://msdn.microsoft.com/en-us/library/aa365247 My  previous post  described how we could create a custom RRT with an AutoStore VB/JScript process script. The scenario began with an AutoCapture date field, its value was formatted as mm/dd/yyyy, and needed to be part of the file name. Those slash (/) characters in the date would not work as-is for the file name. So, the script reformatted the date as yyyy-mm-dd, which is friendly for a Windows file name. In this post, we'll produce that very same result using the Data Filter process component. We'll start with

AutoStore: Create a Custom RRT

Image
Have you ever needed to dynamically create a custom RRT for an AutoStore process? In my previous post AutoCapture Default Date , I described my very first AutoStore script where the value of an  Invoice Date  field in an AutoCapture Vendor Invoices  form was assigned a default value of the day prior from the current date. This Invoice Date  needs to be part of the file name, however its format contains slash (/) characters that cannot be part of the file name. So, we'll use the AutoStore VB/JScript process component to create a new RRT that's more friendly. To do so, we'll look at how to do the following: Bring the existing Invoice Date  value into the script Reformat the Invoice Date  to a Windows-friendly file name Output the reformatted Invoice Date to a new custom RRT After adding the VB/JScript process component in between the capture component and the Send to Folder route component of the configuration file, we open the AutoCapture component to conf

AutoStore: AutoCapture Default Date

Image
I recall the very first script that I ever created for a workflow with AutoStore. The scenario was for a small but very busy accounting team who needed to scan invoices, and have them delivered to a shared folder that was named Vendor Invoices  in a more organized way. In order to demonstrate how an alternative process could work, I configured an AutoCapture Form with three fields to collect the following: Vendor Name Invoice Number Invoice Date The Vendor Name  value would be used to create the subfolder, and the file name would be comprised of the Invoice Number and Invoice Date  values. The next stop was a demonstration for the client. They were able to see a real improvement to their current process in terms of the time savings for capturing invoices, which were estimated at an average of 40 per day. Paired with the ability to easily locate the document at a later time using a well organized folder structure with consistent file naming, all of it was clear and simpl