Posts

AutoStore: Konica Minolta iOption Script Language

Image
Like most recent capture components in AutoStore 7, form behavior can be made to order with the Konica Minolta iOption capture component using a form script. When the script editor is launched, a Visual Basic .NET script template is provided. Looking at the AutoStore Konica Minolta MFP capture component, which interfaces with Konica Minolta device using OpenAPI technology, you also get a .NET script template, so no loss there. However, the language of that template is in C#. For those who have worked with the Konica Minolta MFP capture component in AutoStore, there are many reasons why you might prefer to continue developing form scripts in C# is preferred. What ever the reason, you have the ability to write your form script with either the VB or C# or language in the Konica Minolta iOption capture component's script editor. Here are the steps: In the AutoStore Process Designer, open the Konica Minolta iOption Capture Component. In the General tab, select
Post a Comment
Read more

AutoStore: Reasons to Consider Using the Document Writer

A really great tool tucked inside the AutoStore toolbox is the Document Writer process component. Essentially, it provides the ability to create a text-based file within an AutoStore task. The text produced can include both static elements, and well as RRT values. Here are a few practical reasons why the Document Writer can be so useful. Testing RRT Values Sometimes, we need to confirm the value of a particular RRT as it makes its way through the process. Include one or a group of RRTs in the Document Writer for the resulting text file to reveal the answer. For example, take an unfamiliar process component where the exact RRT values need to be analyzed. Just add those RRTs into the document writer to reveal the output, and it's a great way to get through the testing phase. Testing OCR Text OK, this is similar to Testing RRT Values, but different. Yes, we are testing an RRT value, but not from a logical data point in the process. What's really being tested is the rec
Post a Comment
Read more

AutoStore: Planning Solid Barcode Workflows

Image
Processing barcodes using AutoStore is something I get asked about frequently, and for what would appear to be a pretty simple image of bars and blocks, there's quite a bit worth talking about from a technical perspective. Notwithstanding, actual workflow requirements are key. When building any document barcode process, and considering even the simplest of jobs, there are three main categories of what is actually being processed which deserve to be examined: Batch Document Page Generally speaking, a batch consists of many documents, and a document is made of of one or more pages. Obviously, we can break these items down into even smaller pieces, but these are the basics. With respect to the actual barcode value in the job, there are the actions which can then be taken: Split Keep Extract Knowing how barcodes can be handled, the following 3 questions will help take us to creating the most solid AutoStore process process. What's The Goal? Barcodes can a
Post a Comment
Read more

AutoStore: Why Multiple Tasks Are Needed

Our neighborhood market, the big-mega outlets, airport security screening, the DMV, and the interstate freeway system in most major metropolitan areas during rush hour traffic all have one thing in common: there are never enough open lanes. To the endeavor of order and process, when the volume of activity is not accounted for, regulating the forward flow to a single line creates what we call in the industry as a bottleneck. Stalled movement feels like being tied up in a straight jacket. One way to think about an AutoStore task how a printer prints. After the print command is launched, bits and bytes received by the printer trigger a series of events. Paper is pulled from the tray, the information is applied to the paper, and the final product is placed on the exit tray. Before any print job is completed, the printer is in a busy state, and can't be used. Any other jobs that need to be printed are waiting in a queue, and begin after the printer has finished printing the job wh
Post a Comment
Read more

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
Post a Comment
Read more

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.
Post a Comment
Read more

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
Post a Comment
Read more