Kofax RPA Tips & Tricks

Kofax Robotic Process Automation (RPA), also known as Kapow, is an easy-to-use platform that allows you to quickly set up software robots to replace manual tasks, decisions, and activities. In this webinar, we will share some tips, tricks, and common uses for Kofax Kapow software robots, including accessing business applications, web portals, and local files.

Download PDF

Quinn Huntsman:

All right. Hello and thank you for joining another webinar Wednesday with RPI Consultants. This is our second of today’s double header. Today we’re going to be talking about some tips and tricks with Kofax’s RPA product, which stands for Robotic Process Automation and formerly known as Kapow.

Before we get started here, we’re going to go ahead and introduce ourselves. My name is Quinn Huntsman. I’m a business analyst here on the Content and Process Automation team in Kansas City, Missouri. I have a background in web development as well as Perceptive Content administration and troubleshooting.

I’ve been a part of implementation projects, upgrades and enhancements, so lots of background there. As well as I am a certified Kofax technical solution specialist for Kofax’s Robotic Process Automation product that we’ll be talking about today.

Geoff L.:

My name is Geoff Lilienfeld. I’m one of the partners at RPI and I manage our content and process automation practice. I’ve a little over a decade of experience with imaging solutions, integrating those solutions with financial systems and ERPs as well as designing and developing process automation solutions.

Prior to being in the IT space I was a management consultant. Kind of come from an entrepreneurial background. My fun fact here is I bought and resold 14,000 iPhones in 2008.

Quinn Huntsman: That is a fun fact indeed. What we have on the agenda today, we’re going to get into a little bit about RPI Consultants, tell you who we are. And then we’ll get right to the bulk of the presentation, discuss some tips and tricks we’ve learned with working with Kofax RPA.

At the end we’ll open it up to you all for questions and summary and then at the very end we’ll discuss some exciting upcoming events we have regarding RPA, so stick around for that. About RPI Consultants, we are a full-service professional provider for the industry’s leading enterprise content management and automation software, including Infor Lawson, Kofax products such as RPA that we’re going to discuss today.

And then the Hyland Software suite such as Perceptive Content or Brainware. We have over a hundred full time resources including technical and solution architects as well as project managers who are ready to add value to your business every step of the way. We are based in Baltimore, Maryland, but we do have offices in Tampa, Florida as well as Kansas City, Missouri where I am presenting to you from today.

Some of our technical services include strategy and architecture as well as new installations, upgrades and migrations as well as process analysis, systems design and implementation, managed services, staff augmentation and projects and change management. We can go ahead and start with the bulk of the presentation here and share with you some of our RPA tips and tricks we’ve learned along the way. Without further ado, let’s get right to it.

Geoff L.:

And definitely, please feel free to ask questions too as as we go.

Quinn Huntsman:

Absolutely. You can do that in the GoToMeeting panel and our moderator Michael Hopkins here will kind of feed those questions to us. The first thing we want to share with you, it’s the first place you start with your RPA project, which is designing your robot. A few principles or tips here on designing your robot.

The very first thing you’re going to want to do is step through that process as an end user. That’ll really help you understand what it’s going to look like as far as the robot because truly what RPA does is [inaudible] end-user steps and process.

It will look very similar to that as far as the workflow. Another point here is to keep in mind that you can kind of chain your robots together. It’s a really good idea to build or design one robot with the idea of having one robot execute one task in mind to really keep things organized and clean.

A few other points here that you can identify when you’re designing your robot or identifying variables, things that you need to store, whether that’s usernames and passwords for a login screen or really anything to that effect. Also, it’s important to identify points in the process that absolutely do require a user input or intervention of any time.

For instance, we have a vendor due diligence verification robot that we built that we accept the input for a vendor name, so it’s pretty crucial there. And then the last thing as far as designing your robot is to start to think about how you want to schedule this robot.

Does this