Thank you for joining RPI Consultants Summer Webinar Series. My name is John Marney and this is Michael Madsen, our main presenter. We’re going to be discussing how you can audit your email document imports using RPI’s email capture service.
So first, a little bit about RPI for those of you who don’t know. We’ve been working with the Perceptive platform for around 16 years, and also with the Kofax platform for most of that. In the last year or so, we’ve started picking up the Hyland products as well. We are a Hyland partner. In fact, we have just brought on board the senior architect, Sydney Isle, to help us kickstart our support for those products.
We have around 20 team members in this practice on the imaging team, and we’re headquartered or we’re based out of Kansas City. That’s where we’re broadcasting from today. The remainder of the company around 70 people focus on the Infor Lawson products. Our headquarters are in Baltimore. We also have our Lawson Technical Practice based out of Tampa.
Just a little bit about what we do. Of course, we do a lot of eForm and iScript development enhancements to people’s existing platforms. But we can do from the ground up workflow designs or redesigns. Maybe you’ve been using your product for three, five years, and you’d like to revisit some of your pain points. We also do health checks to help with that. We’ll bring up to the latest version with an upgrade, and of course if you’re coming from a legacy system, we can do a migration and we have a really good team around our clinical and HL7 solutions as well. Mike.
Thank you John for the introduction. So what is the EC service? The EC Service is an email capture service that we’ve developed in-house at RPI. It’s fully customizable because it’s developed in-house. It’s platform agnostic so we can make it work with whatever platform you have or that you need it installed on to. It’s easy to install and we can provide the installer guide at your request.
Another note is that for right now there’s no licensing on it so there’s no cost for you to own.
Yeah, and it has a number of features. This is not integrated specifically with Perceptive Content. This basically will just integrate with your email box to download emails and images. This can be used with Kofax products or Hyland products as well. We can integrate with any type of email inbox, Exchange or Office 365, POP3, IMAP. Of course it can delete emails, it can move emails from folder to folder, it can flag emails as read or unread, just depending on the configuration that you need.
So why is there a need? A lot of people already use a mail agent for their mail processing. We’ve added in some things that we know there’s a need for like auditing, handling unique email types, and customizability to meet your business. For auditing what we mean is that we have tables that store the emails and attachment or the data of emails and attachments that you’re downloading from your inbox, that you can go back to in those database tables to reference, to verify any kind of information that you’re looking for.
In regards to handling unique email types, by that we mean many customers have foreign vendors who may have special characters. With our service we don’t have any issues processing those and we can pull them in normally.
And of course for customizability since this was created in-house, if you have any specific handling you need around certain inboxes, certain file types, certain documents, we can definitely make the platform do whatever you need.
We’ll go through a little bit of the EC Service architecture. The way that we put the EC Service together it basically just runs as a Windows service and leverages its own database. By that what we mean is we can either piggyback off of the INOW database and build our tables out there, or if you have a business need for it you can create an entirely different database for it to connect to, to use to store the information of the emails and the attachments.
That is a significant difference from the mail agent. For the email capture service made by RPI all of our configuration and all the data is stored inside of a database and the files themselves are dropped into the file system. There is a configuration file but it doesn’t contain most of the information needed to set it up.
Right, and the documents that are downloaded from the attachments, once the EC Service downloads those documents, the EC Service is essentially finished with its job. From there the way that we get it into your system is by either using Import Agent or iScript. The reason that we would use either or, you might use Import Agent if you don’t have as complicated requirements for your import process. If we just have literal values that we