Jimmy'sTubeCast Blog

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

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

One of the many great things that make AutoStore so powerful is the Runtime Replacement Tag, better-known by its more familiar acronym as the RRT. These placeholders of information positioned inside the desired location of an AutoStore workflow configuration provide solution designers with the ability to simplify front-end business processes by connecting variable source values to create both well-structured and dynamic routes. Adding RRTs to a configuration is quick and simple. For a given component's configuration properties, set the mouse cursor, and from the list of available RRTs, drag-and-drop the desired RRT. For example, an RRT could variably define the email address that the Send to Mail Recipient should send the message to, or perhaps define all or part of a UNC path for the Send to Folder component to write the file over to. Most of the components in AutoStore have an RRT that show up in the list of available RRTs, as well as a description in its Help file. By mo...

To preface what could be regarded as a very small thing, I am reminded of a common turn of phrase concerning the amount of perspiration that should be afforded to the "stuff" belonging to a particular size-category, and pretty sure there was a book written about that topic. Not to come across as disagreeable, but rather to invite a little balance based on my own general observations over time, an increase in cost with things such as time, money, even relationships, can be avoided when the "small stuff" is given the regard that it deserves. One of these tiny details has to do with string variables that reference folder paths within a script. There are times when it is important that a defined directory for a particular folder should and must always end with a backslash. As an example: folderPath = "C:\Example"   Of course, it really is not very difficult to manually enter that backslash into the path. folderPath = "C:\Example\" ...