Perceptive Experience Content Apps
Perceptive Experience is the next-generation web client for Perceptive Content (ImageNow), delivering content services via a single, adaptable user interface. Perceptive Content Apps are applets that deliver Perceptive Experience. Content Apps are modular in design and can be pieced together to combined platform capabilities into tailored user interfaces.
With more Perceptive Content (ImageNow) consulting experience than any other independent firm, in this webinar RPI Consultants will share more information about Perceptive Experience as well as use cases and case studies for building and deploying intuitive Content Apps.
Transcript
Daniel:
Hello everyone, and welcome to another one of the RPI’s nationally acclaimed Webinar Wednesdays. I’m Daniel. This is Adam. Today’s topic is Perceptive Experience Content Apps. The next generation web plan for Perceptive Content, able to deliver content services through a single adaptable user interface. Content Apps are modular in design and can be pieced together to combine platform capabilities into tailored user interfaces.
So, before we get started with Perceptive Experience, here are some other RPI events you should be interested in. On the webinar front, later today we’ll be discussing migrating your enterprise content and data into the cloud.
Next month we will be talking about what’s new in Kofax TotalAgility 7.6 as well as what’s new in Kofax ReadSoft Online. On the ops side of things, this month we will be discussing Perceptive Content application plans led by our lead consultant, Mike Madsen and next month we will actually be discussing Perceptive Experience presented by our resident expert Adam.
Adam:
Hi, I’m Adam Kinney. I’m a senior technical architect here at RPI Consultants. I come with a bachelor’s degree in management information systems from the University of Iowa and I’ve been working with Perceptive Content for about eight years now. I am the self-proclaimed King of the North, given my remote location in St. Paul.
I’m pretty sure everyone calls me that.
Daniel:
Sure, you can think that.
Hello everyone. My name is Daniel Jenab and I am a project coordinator here at RPI Consultants. A little bit about myself, I received my master’s degree in communications management from George Washington University. I am certified as a Kofax technical solution specialist and Kofax TotalAgility and I’m the de facto office personal trainer and nutritionist. Remember a personal health check is just as important as a technical health check.
Additionally, we should discuss the elephant in the room. As you see with Adam and myself, this is the most heavily bearded webinar in RPI history. So, viewers, you picked a perfect day to tune in.
On the agenda for today’s webinar. First, we’ll give a general overview of Perceptive Experience Content Apps, what they are, and some items of consideration. Next, we’ll move on to our Perceptive Experience case studies, which are firsthand looks at how Adam and other RPI Consultants have implemented Perceptive Experience in unique ways to fit the needs of our clients. From there we’ll get into some Perceptive Experience pre-requirements and whether it makes sense for your business. And finally, we will finish with a summary and questions wrap up section.
Adam:
So, first thing we want to answer is what exactly are we talking about when we say Perceptive Experience Content Apps? Basically, it’s a one stop shop for your document management needs in an HTML5 front end. When we say Perceptive Experience, we need to differentiate that from when we say Content Apps. Perceptive Experience is the platform that Content Apps are built upon. So again, it’s a web based HTML5 front end for your end users. Content Apps encompass things such as capture, workflow, tasks, views, et cetera. There are other Experience apps that lie outside of the Content Apps realm. These include financial processing apps such as invoice approval, healthcare apps, and web scanning.
So, let’s go through a couple of differences. Well, six differences between WebNow and Content Apps. WebNow is a Java-based web client, whereas Perceptive Content Apps are HTML5 based. API calls are made by WebNow directly to the ImageNow server, where Content Apps leverages integration server and restful web services calls to performance actions.
WebNow supports client validation authentication, meaning no external identity provider is needed for single sign on type scenarios, whereas Content Apps does not have that level of interaction with a user’s desktop. So, an identity provider such as Shibboleth is necessary. WebNow does not require HTTPS or SSL where Content Apps does. WebNow can also capture documents via drag and drop or simple file upload. Whereas Content Apps requires web scanning for document submission.
There are a few considerations to be made when you’re deciding when and if to get off of WebNow and onto Experience Content Apps. The first major one being the 7.3 Sunset date of WebNow. this version of content, 7.3 is the last version that WebNow is going to be developed and supported upon. Also, in order to get the latest and greatest features of Content Apps you need to be on Experience or excuse me, on the server 7.3.
Earlier versions of Content Apps 2.4 do work on earlier versions of the server, but with the newest features, 3.0 is only compatible on 7.3 and greater. The server-side Java re