Year: 2016

Watch our video on why ABBYY FormDesigner is a great tool to build your forms from scratch. Its unique features provide the ability for you to standardize the input and get the best results back from ABBYY’s form recognition products. Watch this video to learn more or ask “The OCR Experts” at User Friendly Consulting® how they can help!

Hello. Today I’m going to show you how to use ABBYY’s Form Designer product. This is a neat little tool that is typically complimentary when you purchase the software. It just does a nice job, gives you a basis of creating forms from scratch. That’s really the purpose of this designer is how to create those forms from scratch, and I’m going to walk you through the process.

What we’re going to do is we’re going to just create a new form by going to file, new. I’d like to walk you through the wizard. Now once you’re good at this you don’t need the wizard. You can start on an empty form, but the wizard really provides the basis of a good form. The first page of the wizard is to detect the page size. You can select whatever is appropriate there. Then of course the orientation, whether you want portrait or landscape. By hitting next we get into some of the nitty gritty of good form design. One is we need to determine if there are going to be what we call dropout colors on the form.

Now if you’re not familiar with dropout colors, I would recommend that you do some research on it. But dropout colors are really a method that scanners will drop out a color for your convenience. This does a lot of help for us from a software perspective when we’re wanting to recognize. When we dropout, it could enhance the quality of our recognition when that happens. We could help you there if you need more guidance on the best way to set up dropout colors. It’s very important though to figure that out from scratch when you’re designing a new form because it really will only help you more down stream.

We’re going to stick with black and white, but there are of course other options here right out of the box. The next very important type is anchors. Now anchors help us align a document when it’s being scanned. When it’s scanned, these anchors, and you might be able to see them here in this little diagram, the anchors will tell the software how the document is lined up. If it is skewed a little bit one direction or another, it will line that up. Obviously once it lines it up, it is able to help us a lot better with recognition. Anchors are actually a very, very important type that many people don’t consider when they’re processing, creating a new form. In this case, you can have either a black square or corners. I’m going to keep it a black square just so it’s obvious here on this form. Then we’ll hit next.

Then of course we get to kind of customize our form, what do we want to call this form. We’re going to say this is my new form. We can add an identifier, which if you can see on the little diagram here on the right, bottom right, is a barcode with digits, or you can have just digits only, or just a barcode only. I think it’s wise to have both. The reason that you would want this identifier is this can tell you a specific version of a form, which is typically very, very important because form designs will change throughout businesses and as business changes need, the form itself will change. We want to make sure that we know the exact way to identify this specific form and what is expected to be captured on the form.

You can also add a pattern at the top. We’ll add it just for fun so you can see what the pattern is. It’s really just a, it gives it a key to the user or to the person filling out the form what is expected here. Right out of the box we can add elements very, very quickly to the form. We’ll go ahead and add a couple just for fun. You can see those will automatically be placed on our form for us. Then from here you can hit finish and you can see in front of us we have a nice form that’s already designed for us. I’m going to zoom out just a little bit so we can see the full form, but a couple of very important things. One, here is the pattern, and this is how we tell users what should you provide in the boxes that you’re provided on your form. You can see we have an identifier, and we have our anchors here as well. If you have those anchors, once again that tells the software how to align the form when it’s scanned.

You can see also here we have those fields that were added by default, and we can expand the size. We can also change the location by dragging them any certain place we want. You can see we can put that in the middle. We also of course had a standard tool bar that will tell us, will guide us into if we want those centered or aligned a certain way we can do that as well. This is pretty neat. Now, to go a little bit further with form design, it’s very important that we design boxes that are obvious and easy for us to recognize. We have full control over the design of these boxes here, for the first name field for example. By looking at the element properties, we can set certain properties for that specific element. For the first name, we may, if we wanted for some reason to have multiple rows, which we wouldn’t for a first name, we could, and we have our source size.

Now we call these little boxes here cells, and we’re just going to make those extra large. You can see there it changes. If for some reason you wanted to have those a custom size, you could do that as well. We’re going to … You can set a background, which in this case we’re not going to. You can … I’m just kind of walking through the element properties here as well. You can change anything that you would like. What I’m going to do also is change what we call a marking type. Marking type is what kind of boxes are surrounded. Right now you can see there are dotted boxes, but you can make different types here. I’ll just kind of change these on the fly so you can see the different ones. The software does very well no matter which of these types you do. We have had best experiences when you use letters and frames. You can also do letters and separated frames, but either way we have had the best experience with our customers when they use letters and frames there.

You can see here you can modify every single field that you’re capturing with these element properties, so you can have full control over it. Now I’m going to not go anymore into those properties because I think this is a great way for you to learn, and you can try different things and have fun with it, but on the left here you can see a toolbar. These are the different types of field you can put in. Of course what we have in front of us, the ones that were on the form by default, were text field. If I click and drag it there, you’ll see it’s just a text field. We can have a date field. You can see you can setup a hint, is this month, day, or year. Of course we can have check boxes, or we can have a series of check boxes if we wanted them in a certain list. Just a neat little option there. Of course you can put in the text here all around, so you have full control over the design of the text that goes into there as well.

Then the neat part is if you wanted to create your own table, you can implement your own table here by just kind of following the standard and walking through that wizard there. You have full control over that as well. And there’s some more things here. You can also place an identifier. This is the form identifier. If you didn’t like it there, you could create a new one and place it otherwise. It’s a lot of good things and kind of fun things. You can also drop an image on here and create an image maybe to add a company logo or something like that. This is the Form Designer. You want to make sure that you save different versions of this because you might like a certain version, and you might be playing around. Definitely do a good job and keep your backups.

Once you’re done, however, you can export this to any format you want, including a format that can be consumed by ABBYY FlexiCapture, or you can export to a fillable form with PDF. If you wanted to distribute this and you wanted it fillable where it has the different columns that we’re able to type into on a PDF document, like Adobe Acrobat, you can do that as well. I would encourage you to look and play around with ABBYY Form Designer. It is a very neat little product. Once again, it comes complimentary with many of the versions of ABBYY FlexiCapture that you purchase, so you might already have it installed, but you just may not have messed around it. Go in, it’s a very cool tool, and take advantage of these neat little features that you can use within ABBYY FlexiCapture. I hope you enjoyed the video. If you have any questions, please let us know. Thank you.

Related Content:

Save

Watch our video to learn how to create rules and custom actions within ABBYY FlexiCapture. Rules are triggered when data changes, and custom actions are triggered when a user clicks a button.

Hello. Today, I’m going to show you how to create rules and custom actions within the ABBYY FlexiCapture.

Now, what you see in front of you is a ABBYY fixed form. This is just a very basic document definition. Sometimes we call it a template, but that’s not really the point today. The point today is how we create the rules and custom actions. We have other videos that show you how to create this form, and, in fact, even the project that goes around this form. You can find that on our website if you’d like more details on that, but today, let’s focus on those rules and custom actions.

What we’re going to do is create a new field. What this field is going to do is going to merge first name and last name. We’ll call it something like full name. It’s going to put first name, space, last name. That is what we consider a rule. Now, the difference between a rule and a custom action is that rules happen on the fly, as data changes. A custom action actually requires user input, and you’ll see that here, the button that we create here in just a second.

But the very first thing we’re going to do is create a new field, and we’ll give this field a name first, and we’ll call it something like Full Name. Then we will add a rule. The rule that we are going to use is a merged field, because we want to merge first name and last name, but you can see there are other types of neat rules here, including calculations or comparing fields, but, in fact, you can write even your own script. But, once again, remember that these rules happen on the fly as data changes, so you do want to be a little bit conservative on when you implement your own custom logic versus what you can do out of the box within FlexiCapture, but a lot of cool options here.

For today, we’re going to merge these fields, and we’ll just call this our merged fields rules, and we’ll actually give it a proper name, Merge First and Last Names. You can see here just some of the out of the box options, if we want to show this as a message to the verifier, when we want to apply this rule. We can set certain conditions so that a certain field is not empty, and those kind of things. But for today, we’re just going to leave this as the default.

Then you can see we have tags here. Tags are just used as shortcuts for finding it in the future. If we have a lot of rules, it’s important that we tag, so we can find them easily. Then, of course, we want to make sure that this rule is enabled, so we’ll click Next.

We’re going to add fields that we want to merge. Now, this is obvious, because we know that we have first name and last name. Select first name, select last name, and you see there it populates it in our Fields to merge list box. It’s going to ask you the resulting field, which is going to be this, which is where we’re at here. We’re going to put, what do you want to separate those? I’m simply going to type a space. Then, of course, we have the option here to put separators for empty field values, which we’re not going to select for this, and we can simply hit Okay, and we’re done there.

You can see here that the rule is applied. We have our Full Name option here. Now if we go and we run a test, and we just start populating data here, you’ll see that it does our merging fields here. We can even put first and last, and watch how the Full Name field gets modified as that happens. I’ll do it one more time. I’ll do John and Doe, and see how the Full Name field here merges those two with a space deliminating the two words. So, a neat little option there. That is a rule. Once again, you can see it as I type, it modifies the merged field option here.

Now, the next thing I’m going to show you is how to create a custom action. Now, custom actions require a user input to trigger that action, and what we’re going to do is create a new field, and we’re going to call it Approver. You can see here that the Approver name then happens right here.

I’m going to modify the field after we added it, and we’re going to create a custom action. You can see the custom action is right beside the rules, so we’re going to enable it, and these are the available fields. Sometimes there is logic from the form that we want to use within the custom action, so for example, we may want to use Full Name. We can see that when we have them marked as read only, it means that we only have access to that field, but we cannot modify the field, which is a little bit different here. We actually want to be able to control the Approver name, so we’re going to actually make sure that that’s read only for us.

But, for Full Name, we just want access to that field, so we don’t really need it to be writeable for us, so we’re just going to leave that as read only, and then you see here, we can go into the scripting. The scripting within ABBYY FlexiCapture is very, very powerful. It’s very neat, and I would recommend that you use some free time of yours to investigate it and learn it, but all I’m going to do is simply write a very basic script. I’m just going to copy and paste it here, and I’ll walk you through it.

What we’re going to do is we’re going to show a message box, and then we’re going to say, “Do you want to approve this time sheet?” It’s going to prompt them with a Yes or No, and if they hit Yes, equals Yes here, then we are going to modify this text box with the user name that is currently using FlexiCapture, and a date and time. It’s that simple.

Notice how in the other window before us, we put what other fields we want to have access to, and the reason we may want that is because we may want to pass those fields to our logic. For example, we may want to create a variable here called Full Name, and what we’re going to do is … Oops, excuse me. You can see here we may want to access that field. We may use this now within our message box here to say something like, “Do you want to approve the time sheet for …” Use that. Something like that, so what it’s going to do is simply use the Full Name within a variable, but then we can use that variable in our logic here.

I’m going to take this away just for one second. Notice that we only have access to two fields, even though there are multiple fields on this document definition, but these are the ones we told the rule that it has access to. This one, of course, you remember is read only, where the Approver is not. The Approver name is something that we have full access to control.

Once again, we’re just going to prompt the user, “Do you want to approve the time sheet for …” whatever the Full Name is, and then we’ll get a Yes or No, and then if they hit Yes, we’ll populate the field. So, it’s very, very simple.

Now, what I recommend doing every time you write a script is that you hit the check button, and you’ll see here that it is not complaining about our code, it likes it. It says the “Script is correct.” If there is a problem, however, you’ll have to make sure you resolve that problem before moving forward. We’re going to hit Okay, we’re going to save, and then we can close this.

Once again, having the Approver name not read only is very important, because we actually want to populate that field. If it’s read only, we don’t have the ability to populate the field. Let’s hit Apply, let’s hit Okay, and let’s watch these two rules and custom actions run together here as we do a test.

Let’s populate a first name. We’ll say John Doe. Remember the Approver name is the one that’s going to prompt us with a message box. Now, notice this little box over here that has the three dots here. That is our custom action, so if we have a custom action that we want to perform, we click that box, and you’ll remember, this is the message box that we wrote. It says, “Do you want to approve the time sheet for John Doe?” Of course, if I hit No, it’s not going to do anything, but if I hit Yes, it’s going to populate this field with the current user’s name plus a time stamp that tells us when that was approved.

So, that is the idea of rules versus custom actions. Both have their place throughout the business process within FlexiCapture, but I wanted to show this to you today to show you how advanced the tool is, and how easy it really is for us to apply our own logic right out of the box.

I hope you enjoy this video. If you have any questions on rules or custom actions, feel free to contact us, and we’d love to be of service to you. Have a great day. Thank you.

Related Content:

Save

Save

Watch our video on how to create your very first ABBYY FlexiCapture fixed form project with a special focus on handwriting.

Hello. Today I am going to explain to you how to create your very first ABBYY FlexiCapture Project, but this time focusing on just handwriting projects. Now, if you have a machine printed project, we have another video on our website that will show that for you. Let’s start with just handwriting today.

I’m going to open up the sample that we’re going to use in the project, and I want to explain a few things to you before I do that. The first thing I want to point out is, notice these anchors here. There’s some anchors and there’s also a barcode with an anchor beside it. These things are very, very important when it comes to designing a form. In fact, it’s very wise to include anchors on your form, especially if you’re able to have control over that form and start from scratch, because it helps the software line up with the way that the image was scanned.

The other thing that I want to show you is that we have some text boxes here. Our OCR quality, or what we actually call ICR with handwriting, is much, much higher when we have control over the constrained fields, is what we call these boxes. When you have the user writing in what we call these constrained fields, the IC quality simply just goes up, and we have a much better result from the software when we have a special zone that we can read from without just a simple line that the software’s expected to read.

We typically call these framed boxes or sometimes even combed boxes. You see here on the top, we have first name, last name, and badge ID that I have a solid border. Then I’m going to zoom in just a little bit, and you may be able to see this on the video, but these dates, start time, end time, and job code fields have just dotted boxes around them. Once again, any time we can do a constrained field the better, so I just wanted to point that out.

When you’re creating a form, consider things like constrained fields and anchors, and maybe even a barcode or some type of versioning tag that tells us what version of the form this is, because forms are living documents. They do change and the needs of your business changes, and somehow that we can detect this for versus a similar but somewhat different version of this form is very important when we’re talking about OCR or ICR recognition.

What we’re going to do is use this form today to create our very first handwriting project. We’re going to open up our ABBYY Project Setup Station, and we’re going to create a new project. We’re going to create this in a demo folder. We’ll just call this our demo project. You can keep these settings, the save as type and the project type, defaulted here. We’re going to create our very first one. We have it now created. We’re going to go to project and we’re going to do a document definition. Sometimes we call document definitions templates. This is where we tell the software where to capture information off of these documents.

We’re going to hit new and we’re going to call this our time sheet document definition. We’re going to leave the language and the writing style alone. You can obviously change these to be for the standards of your form. Since we’re focusing on handwriting today, we’re going to go ahead and also leave the ICR option selected. Once again, you would use OCR if you were reading machine print off of a document. For today’s demo, we’re going to stick with ICR. We’re going to go next. We’re going to load a blank page that we would have already had scanned. We’re going to hit next. We have check marks that are auto-detected or text that are auto-detected, and I’m just going to go ahead and not select either of those for today’s demo.

Okay, so we have our document definition created, and now we need to simply tell it where these fields are. We would just use our elements up here to determine what kind of fields we are dealing with. You see there’s a couple different fields. We have text fields here and we also have a table. For the text fields, we’re going to just select the text element here and we’re going to just lasso over where that text is. The software does a pretty good job, typically, of trying to name the field here what it recognizes as the text. When we did lasso over it, you see here it added the field and it gave it the name that it found beside it, which is first name. We’ll do the same thing with last name and we will finally do the badge ID.

Now, the important thing also when you’re dealing with ICR is that you review the properties of the fields. Notice down here the marking type. This is very, very important. This is where we tell the software what style of boxes these constrained fields are. You can see the different options here that you have in the software. We have what is considered a car box series, but you can see, and you’ve seen forms like this in the real world that look similar to this. Once again, anything we can do to constrain that field, to tell the software that this is the boundaries of a field, the better it will do. We’re going to just leave that alone, and you will see here, you have control over how many cells that box should be. We’re just going to leave that defaulted. It will automatically detect the number of boxes. That’s a very, very important thing to do when you’re first creating your form document definition.

There’s our first three fields. We’re going to go ahead and save, and then we’re going to create what we call a test batch. Test batches are simply what they’re called, they’re just testing. It allows us to use the document definition window as a quick testing ground for real forms. I’m going to simply just drag and drop our first sample here. We’re going to let the software detect it. There, it’s done.

Okay, so what you see here is the fields trying to detect where they’re at in the form. Of course, this one doesn’t detect any of these fields correctly. The reason why I want to show that to you is because we didn’t tell the software that this form and this document is allowed to be scanned in multiple different orientations. All we need to do is hit our document definition properties and tell the software that the page is possibly oriented in these different ways. We’re going to select all three for today’s demo, and you would select which ones are relevant in your environment. Now we’re going to save.

We’re going to go back into our test batch, and we’re going to rerun the results of this. All right, so now we can take a peek here at what the results were. You can see, there they were on the different results, what we captured there. I have a couple other samples we’ll run, I can just simply drag and drop them and we’ll look at those results, too. Once again, we only set up the software initially to read the first name, last name, and badge ID. There’s the other one, and the last one that we did as well. You can see, the software does a very, very good job when we have constrained fields here.

The last thing I want to do is show you how to set up a table. Now, this is obviously not the same on every project. Sometimes you will have tables and sometimes you don’t. It’s important to work with your account rep to understand implications of what having tables does on licensing and things like that. I do want to show it to you so that you’re aware how to create tables. It’s very easy on what we call a fixed form like this. All we need to do is select the table element, and then we kind of just lasso over this table.

Now, the neat thing that we can do is we can right click once that’s created and tell the software to auto-detect vertical and horizontal fields. Maybe you can see okay on the video that it then put a blue line here between all of the fields. Actually, this is a date field so we’re going to remove that separator. We can do that by just clicking here and removing that. Now the software knows this table, but now we got to tell it the different columns. All we’re going to do is select the text element and we’re just going to select these columns. You see, we’re going to do them one at a time. Now we can rename them. This would be date, excuse me. Date, start time, etc. That’s how you create a table.

Now, this is pretty much the conclusion of the demo, but there are a couple things I want to show you here and restate one more time. The one important thing is that we always control anchors and we always control some sort of versioning technique, in this case it’s a barcode. We can also read barcodes and things like that with the software.

Remember, when we’re talking about text fields, we want to do as much as we can to tell the software about these text fields. We want to tell the software in the properties why kind of type we’re looking at, we call that the marking type. Also, it is very important if we can tell the software what kind of field text we’re looking at. What is the data type? Obviously for a first name and last name, we know those are just text. Maybe for badge ID that’s only a number, and we can tell the software to just consider it a number. What that does, obviously, is it gives the software more control about what the kind of data it’s expected to receive in that field, therefore giving the quality of the ICR or OCR just a higher in significant advantage compared to just every character in the world.

Those are a couple things important to remember when you’re creating your first handwriting project. I hope you did learn a lot. There’s a lot of cool things we can do with this software. This is just a very, very basic beginning. Really, your features are endless within the software and we’d love to be of service to you if you have any questions. Thank you.

Related Content:

Save

Watch our video on how to redact sensitive data using ABBYY FlexiCapture.

Hello. Today I am going to show you how to use ABBYY FlexiCapture software to redact sensitive information on your documents. The first thing I’m going to do is open up my document definition within the software. This is what we call sometimes a template. This is where we outline the fields that we want to capture off the document. I’m just going to simply open my first document definition here. You will see that we have our health insurance claim form, which obviously may have a lot of personal and private information that we do not want transported with the document as it moves downstream in our organization.

Our process today is going to capture information off of these forms, and we are going to block out the insured’s ID number. That’s possibly a private number that we don’t want other people to know. Also things like social security numbers, credit card numbers, are very common things that we would not want redacted.

All we do is we set up our form to extract these details. If you’re not sure how to do that, please go look at some of our other videos. We show some very common examples of how to set up a document definition. But for today’s purposes, we’re going to assume that’s already done. We’re going to go to our export settings. The reason why we’re going to say that is because during export, we want these fields to not be visible on the document.

Now, you’re going to see a couple things. You’re going to see us export the data to Excel. That will show us the details that we want. But on the actual document itself, as it moves downstream in our organization, we will not be able to see this number here, the insured’s ID number. We will actually make sure that is redacted and not visible to the end user as they review the document.

All we need to do is modify our export settings. We can kind of just read through this. Now, realize there are two different things we’re exporting. We’re exporting the data that we extracted off the form, and then we’re actually exporting a copy of the form itself. The data will go one place, and the image will go its own place. Most of the time the data will go into some sort of back end database that we’re using, and a copy of the image will get stored in an image repository. SharePoint or Filenet or other common repositories that are used throughout corporations today.

The first part is going to deal with our data. What we’re going to tell it is what format we want the document to be saved in. You can see we’re just going to keep it Excel, but you have a ton of different options here. We won’t go into all of them today. But you could feel free to request a trial from us, and we’d love to show you these. It’s going to ask you how you want the folder structure and file name to be used, and you can see the different options there. We’re just going to go ahead and leave it alone for today’s demo.

It’s going to ask us where we want the data to be saved. Then how do we name that saved data? Then also if that file already exists, what do we do? Do we add a suffix? Do we add to the end? Or do we rewrite the file? That is the data. Once again, every piece of extracted details off the form.

But when we actually want the form to be saved in its own copy, then that is where we have to click the Save Document Images button. You can see it highlights a couple things. We’re going to just save it to a data folder, but you could also save to its whole other place or location. We’re going to determine the format, and we’re going to go ahead and select PDF A for this one. Being A is the archivable format of PDFs. You see here there are tons of options that we can do when we select the image format. We’re going to leave it alone, but I did want to bring your attention to this screen to make sure that you know the different options that are available to your organization within the software.

The redaction piece of it though is the most important part for this demo. You’re going to see that we have this checkbox that says, “Redact sensitive data on images”. We’re simply going to select that. Then the Select Fields To Redact button is highlighted. We can move the fields from the left to right for the different fields that we want to be redacted on export. We’re simply going to say, “We want the insured’s ID number to be redacted”. But you can see here, you can select any other details. You can select as many of these fields as you want to be redacted. But we’re going to keep it one for today’s demo.

We’re going to go ahead and click Okay. Then we’re going to go ahead and hit Okay there, and also hit Okay. What we’re going to do is save our document definition. We’re going to publish it. Then we’re going to run a copy of this. What I’m going to do is drag and drop a CMS 1500, which is a copy of this form. A healthcare form. You’re going to see a couple of things here. The software’s in the process of processing the document. Now it is completed, and you’re going to see first what it extracted here on the left, versus a copy of the actual file here on the right.

If we zoom in a little bit here, you can see we captured the ID number. But over here in yellow, when we export this document we do not want to see that on the document. This document’s going to live further downstream, and we do not want users seeing that as they use this document for research.

You can see the different details here. What I’m going to do is export this. Now, I have an export folder set up. We’re going to export to this export folder. When this happens, we’re going to take a peek at the document. We’re going to see that it’s redacted. Then we’re going to take a peek at the data and see that we still have the data. We can do with that data whatever we would prefer.

I’m simply going to highlight and export, and I’ll open up our export folder here. You can see we already have the batch there. Once this is completed, we will take a peek at that.

Okay. Now that it’s completed, we will open up two things. One is, I’m going to open up the Excel spreadsheet, which is what we decided to export to. I’m going to go ahead and expand these columns. The important thing I want you to understand is that we still have access to the data. The insured’s ID number, we still have access to. But the other thing I want you to note is that on this document here, it is no longer available to us. Let me zoom out just a little bit. You can see here, the insured’s ID number is no longer visible to the end user. This gives us a way to control the document, and the private and sensitive information that we do not want known to those people that will be referencing this document in our companies later on.

Once again, it’s as simple as setting up export settings that give us the option to redact sensitive information. All of that is done from the document definition. If we go to document definition up here at the left, we can go to export settings. Once again, right here in the image export, is where we can redact that sensitive data on images.

I hope you enjoyed this video. I hope it gave you a good reference point on how to start with redaction. If we can be of any service to you, please feel free to contact us. Thank-you so much.

Related Content:

Watch our video on how to create your very first ABBYY FlexiCapture fixed form project.

Hello. Today I’m going to show you how to create your very first project within ABBYY FlexiCapture. Before I get started, I will let you know I’m using the distributed version of the product. There is also a standalone version of the product, and although things are very similar between the two, there might be slight name changes and some title changes to the applications. So let’s get started.

What I’m going to do is create a new project using file, new project, and I’m just going to browse to our desktop and we’ll call this our test project. The software is then going to create the project for us, and we’re going to go to project, document definitions, new. Today, we’re going to do a fixed form, which is a form that looks the same every time. In other words, the structure of the form does not change, and we’ll hit next.

We’re going to go ahead and load an image from a preexisting file. You can use a physically scanned piece of paper if you want using the scanner option. But for today’s demo, we’ll use the browse to an image file and select a sample. We’ll hit next, we’ll call this our direct deposit form. Before I hit next, I just want you to see the form here. I’m actually going to load it up on my screen. This is a very basic fixed form, and you can see this is pretty standard. And we’re just going to capture a lot of this metadata here on this document to get us started.

So I’m going to go ahead and hit next. This allows the software to automatically detect certain fields. For this demo, let’s go ahead and leave those off, and we’ll hit finish. What the software will do at this point is take us into what’s called the document definition editor. And within this editor, we will see our sample. What I’m going to do is browse to our elements options up here. You can see we can extract text, checked boxes, even a group of checked boxes, barcodes, pictures or tables. What I’m going to do is extract the first name, last name, and employee ID for this given demo. And there’s a couple of different ways to do this, but for this case, we’ll hit create text. And you can see here I’m going to just go ahead and draw within this box. I’ll do that here within the last name, and I’ll also do that here within employee ID.

Now, understand every field has properties, including things as basic as giving it a name; data; type, including is it text, is it a number; how the software recognizes the field, is it hand print versus text printed; how picky the software should be on its confidence level. So should the software treat a character with higher confidence or lower confidence? We can even set rules on what are called custom actions, and those are some advanced demos that we can do at a later time.

So what I’m going to do is just go ahead and just set up each field with its name. This is our first name, second field is our last name, and employee ID. At this point, you’d want to finish this form and continue adding the different styles that we have here, whether it be checked boxes or even tables if you’re extracting them. And what we can do is perform a test. When we perform a test, it’ll perform the test on this specific form that we’ve loaded within the document definition editor. And you can see the software has extracted those fields with very high confidence. It did a very nice job. At this point, if that’s all we were going to do, we would hit save, and we would close our form. Once we get back to our list of document definitions, I will hit publish. Publish will give this document definition the ability to be used for all processed documents moving forward.

And for cases of a test, what we will do is we’ll go to our view and test batches, and we’ll create a new batch. And we will load samples. Now that we have one created for the document definition, we will be able to process these. And you’ll see here, as I select them, the software will them show us the employee ID and first name and last name, and at this point, we have a successfully created document definition and project.

From here, we will go to file and upload, and we will then upload this to our server. At that point, we have a fully functioning project ready to be used in a production environment.

Well, I hope you enjoyed this video. If you have any other questions, please feel free to reach out to us. Thank you so much.

Related Content:

Save