Watch the Demo: Kofax TotalAgility

Kofax TotalAgility (Kofax KTA) is a highly flexible and versatile content and business process automation platform that combines intelligent data capture with advanced OCR, digital workflow management, and process intelligence. Kofax KTA provides transparency and efficiency to complex process lifecycles and dynamically integrates important content and data with your ERP or ECM systems.

Download PDF

I’m gonna give an overview of TotalAgility today. TotalAgility is made up of two parts. Again, it’s 100% web-based. There is the aspect of the designer, and the designer is where all the development and solution building will be. And then, there’s the workspace. And the workspace, again, is gonna be web-based, and it’s where your user experience and end users would take advantage of the system.

So, I’m just gonna go ahead. And you can login via a regular login form, there’s Windows active directory sync, there’s [inaudible 00:00:39], there’s tons of aspects and ways that you could authentic. So, I’m gonna login. I’m using Windows Authentication. And when you first login, then what you’re met with is the dashboard, and the dashboard is gonna be made up of your process designer, your form designer, resources, data, monitoring, integration, system settings, packages, insights, which is like analytics, and so and so forth.

And each solution is made up of a combination of configuration of each of these pieces. And for each piece then, we’re gonna start with the process designer. And the process designer, when you first login, you’ll have two aspects of creating a process. There’s the case, and then there’s a business process. The main difference between a case and the business process is that one is more dynamic, so it’s something like any type of clean process, or maybe a doctor’s visit, something that you don’t know exactly what the outcome might be every single time, or there’s some other dynamic pieces, then you would build out a case.

Then there’s the process, and the process is just something more repeatable, something more predictable. So, the process does take into consideration that it is always occurring every single time, the same process over and over again.

So, pretty much we’ll start with the process. And with the process, this is the designer of a process. So you have like, you’ll name it. You have a type of business process. I could go in. It’s like click on this, then I could build out various nodes. I’ll just click on that node which will create an activity. That activity could be one of many various things. The capture activity is usually one of the first things from the process standpoint. There is the extraction, classification, image processing, export, transfer, validation, scan, and you configure those things based upon a bunch of different variables that would need to be configured.

And then once you go back into the common activities, you have tons of .net activity, create new jobs, web services, tons and tons of different options to go into. And then you would continue to build out the solution based upon the business rules that you need. And once you build out those things, then that would create your process. And each of those processes would have various forms, various activities, and other options that need to be considered.

I’m not gonna save this right now, I’m just gonna jump into the next aspect of the system, which would be your form designer. Your form designer is going to be where you would create your forms, your login forms, your sites. You could have different sites for different processes, or different business units, or what have you. And then, you’ll have various activities, create new jobs activities, login activities, document activities, scan activities, all of these things are based upon various activities. Then you could also work with your MFPs, or your multifunction devices where you can have also native support for several different models as well.

So, I’m just gonna kind of give you some overview of these forms. So, you have a general header form, and that’s gonna be like what you would login and see at the top. Then, you’ll have a login form, which that login form will look like whatever you create it to. This is just a sample of where you would type in a username and password. Then, you have a validation form. This is an in-voice validation form, and what you’ll see here is that when it loads, you have various fields, and each of those fields you could add tons and tons of actions to.

Again, 100% customizable. These actions, you could create new actions, and then you could choose from several different types of actions. You could evoke different .net DLLs, you could add roles for if you have any type of table or columns, you have Kapow integration. You have many, many different aspects to this syst