AutoStore: AutoCapture Validate Regex

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 Form_OnValidate(Form)
    ' Get the field value ...
    Dim strFieldValue : strFieldValue = Form.GetFieldValue(FIELD_TO_TEST)
    ' Test the field value ...
    If Not IsValidRegExp(strFieldValue, REGEX_PATTERN) Then
        Form_OnValidate = "Please check the [" & FIELD_TO_TEST & "] field entry."
    End If
End Function

'================================================================================
' HELPER FUNCTIONS
'--------------------------------------------------------------------------------

' Test a Regular Expression pattern, Return True or False
Function IsValidRegExp(TestValue, TestExpression)
    Set objRegExp = CreateObject("VBScript.RegExp")
    objRegExp.Pattern = TestExpression
    objRegExp.Global = True
    If Not objRegExp.Test(TestValue) Then
        IsValidRegExp = False
    Else
        IsValidRegExp = True
    End If
End Function



If the input value does not contain an ampersand, the form will not submit.



Let's take a closer look at the regular expression pattern used for testing. It will match if the input contains an ampersand (@) along with one or more characters before and after it.

Const REGEX_PATTERN = "^\S+@\S+$"
'--------------------------------------------------------------------------------

' ^             <-- Match the beginning of the string
' \S            <-- Match any character that is not a whitespace character
'   +           <-- Match 1 or more in the preceding Character Set
' @             <-- Match a literal ampersand character
' \S            <-- Match any character that is not a whitespace character
'   +           <-- Match 1 or more in the preceding Character Set
' $             <-- Match the end of the string


For matching an email address, this pattern is not overly restrictive. It's worth mentioning that building an regular expression pattern to test for a valid email address is not only a challenge, but is a highly debated topic.

Consider the growing list of top level domains now available. Gone are the days where .com, .net, .org, .edu, .gov, and .mil where almost exclusively in use. Now, countries have their own top-level domain, plus over a thousand new custom domain names.

The goal for this post is to describe a simple approach to input validation in an AutoCapture form. In fact, with a few modifications to the constants in the script, validating common entries like a phone number, a zip code, or even other custom input types, is also possible.

Comments

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