Jimmy'sTubeCast Blog

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....

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...

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...

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 AutoCap...

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 c...

Regardless of the programming language, a looping-statement is a common declaration for iterating through collections of things, such as the items of an array, records selected from a database, elements within an XML file, or the files inside a directory. A recent AutoStore challenge was presented where a script was used to fetch data in a process that returned either one or many items. This was the easy part. However, each return record needed to be specific to an individual Route based on one of those items returned. Example Example1@email.com Example1/URL Example2@email.com Example2/URL Example3@email.com Example3/URL Although the captured document being processed would be common for all in the return, the recipient belonging to one of these unique records should not be aware of  nor  receive any of the information that would belong to a different recipient. Because an unknown number of return records would be expected, this presents a challenge due ...

If Runtime Replacement Tags (RRTs) make an AutoStore configuration come to life, then workflows can get a bit more clever when Smart RRT technology is used. The Smart RRT is not a new gadget, but these little wonders can come in handy. What is a Smart RRT? As a placeholder for information, an AutoStore RRT has an RRV, which stands for Runtime Replacement Value. We can take a user-defined RRT, also referred to as a FRTN (Field Replacement Tag Name), and inject VBScript into the RRT to quickly modify that tag's value. The result is a Smart RRT. A Smart RRT is certainly not the only way to modify the value of an RRT. The VB/JScript component allows a custom script to be used to generate a needed value based on a metadata value, and the Data Filter component also provides several filters to do the same. There are cases where implementing a Smart RRT may generally be a quicker approach if a given workflow can benefit from the RRV of its modified RRT. We'll look at some ex...