AutoStore: Data Filter Reformat Date


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 a configuration that contains AutoCapture capture component, the Data Filter process component, and the Send to Folder route component.


Go to the Data Filter process component through the capture component by selecting the form. Our example form was named Vendor Invoices with the following fields:
  • Vendor Name
  • Invoice Number
  • Invoice Date

In the Data Filter configuration, set the Activate selection to Yes. When we click on the Add button, a list of various filters is displayed. For this example, we'll choose the Format Date filter.



This opens up the Format Date filter dialog, and there are three primary fields to configure.
  • Field name – This is the name that will be used for this filter. The name we assign here will show up in the Available RRTs list for the Data Filter.
  • Input – This field is for the value that will be reformatted. This input value must be a date expression, and would be an actual RRT in useful cases.
  • Format – This is where the date format is defined.



There's also a checkbox to fail the job if the input or the output is invalid. Given that we're working with the Format Date filter, it will try to reformat a valid date expression, so anything that cannot be evaluated as a date would cause a processing failure.

Here are a few examples of valid date expressions for input:
  • 10/27/15
  • 10-27-2015
  • October 27, 2015

We'll configure this filter to reformat the value of an AutoCapture date field named Invoice Date which would have a date format of mm/dd/yyyy. So, we'll enter "InvoiceDate" into the Field name textbox, and add the AutoCapture RRT to the Input textbox.



Special date-parts that would make up a desired date format would be added to the Format field. When you click on the Insert button, a list also provides some preconfigured formats to choose from. Choose the yyyy-MM-dd option so that no slash (/) characters part of the date.


Selecting one of these formats then adds those date-parts into the Format field, including those static hyphen (-) date separation characters. Each respective date part is preceded with a percent (%) character, and is represented as a single character.



Click OK to complete the Format Date filter setup, and OK again to complete the Data Filter process component configuration. Now, the Data Filter InvoiceDate RRT is available for use. The following example represents the file rename schema for the Send to Folder route component.

~ACC::%Invoice Number%~ ~DFT::%InvoiceDate%~ ~STF::Counter~~STF::FileExt~

The configuration is now completed, ready to be saved, and tested. We should now see the date in the file name formatted as yyyy-mm-dd.


In earlier days before AutoStore 6, one needed their scripting pen to do so many things found in the Data Filter, such as reformatting a date value to pass downstream to other workflow components. Today, the Data Filter makes it fast and easy to tighten up an AutoStore configuration.

Comments

  1. José VillaNovember 10, 2016 at 3:52 PM

    Gracias!

    ReplyDelete
  2. José VillaNovember 10, 2016 at 3:57 PM

    Im Evaluating autostore 7, but i need to use cover sheets with barcode name of document, using barcode process, i have not found any sample to implementing, do you have some one? thanks

    ReplyDelete
    Replies
    1. UnknownNovember 14, 2016 at 7:58 AM

      Thank you José. Check out the following video I did in July 2014 which runs through the basics of the Barcode process component:
      Barcode Page Split
      https://www.youtube.com/watch?v=9LSt7AG1JGE
      Hopefully, you will find it helpful.

      Delete
    2. José VillaNovember 16, 2016 at 1:01 PM

      Thanks a lot, it works for me, the only question is, how can manipulate barcode value on Form_OnValidate(Form) in a autocapture form?

      :D

      Delete
    3. UnknownNovember 16, 2016 at 2:04 PM

      Hi José, the document goes into the Barcode 'process' component only 'after' the document has been captured. Given that, we really would not be able to do anything with the barcode value on the document itself while it is being introduced into the 'capture' component, which would include Form_OnLoad or Form_OnValidate event handlers.

      That said, 'QuickCapture Pro' is a scanning application which uses the AutoCapture component. QuickCapture Pro has the ability to read the barcode on the page, and the user can 'snap-in' that barcode value (even text too) into a form field by clicking on it. Now when the job is submitted, any code you add into the Form_OnValidate event can be called.

      Delete
  3. José VillaNovember 14, 2016 at 12:05 PM

    Thank you, i will check it out,
    best regards

    ReplyDelete
  4. José VillaNovember 14, 2016 at 12:47 PM

    another stuff, my process is docushare, but i need to evaluate name of document to validate captured metadata, well i'll first check that video.
    regards

    ReplyDelete

Post a Comment

Popular posts from this blog

VBScript: Ensure Backslash Folder Path

Image
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\"
Read more

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
Read more

AutoStore: Workflow Loop Example

Image
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 to the fa
Read more