Transcript:

Keith:
Good afternoon, everyone. My name is Keith Wayland from RPI. I want to thank you for taking the time to attend the following webinar on upgrading from ImageNow to content 7, the changes and challenges. We have some excellent presenters for you here today: Mr. Jeff Jones, Geoff Lilienfeld, and Victor…

Victor:
Kovalev.

Keith:
… Kovalev. Sorry about that. Before we get started, just a few quick housekeeping notes. First and foremost, you should be seeing a live video feed. You should be able to toggle between the video and the PowerPoint to your liking.

Number two, questions are encouraged. Anywhere throughout the presentation, type them into the GoTo webinar questions box. Mr. Greg Pollard here behind the scenes will ask throughout. We’re going to try to stump our presenters as best we can because they love that.

Third, and most importantly, we are recording this session. We will be loading it onto our website and to YouTube. It takes us a couple days, but we will send you an email with a link that you can re-watch it or share it with your colleagues. Without further ado, I give you Jeff, Geoff, and Victor.

Geoff:
Thank you very much Keith. Again, I’m Geoff Lilienfeld. I head up RPI’s ISTS practice, Imaging Strategy and Technical Services. We provide consulting around Perceptive products, including ImageNow, from both technical and functional standpoints. We have been working with ImageNow for 15 years, so we’re extremely familiar with it. We are based out of Baltimore, Maryland, which is the office that we stand in right now. We also have satellite locations in Kansas City, Scottsdale, and Tampa. I myself am out of Scottsdale.

Like I mentioned, we’ve been doing the consulting on the Perceptive stuff for 15 years. The majority of RPI outside of our practice consults around Lawson. With that being said, we also consult both Brainware, also known as Perceptive Intelligent Capture, as well Kofax KTM. If you utilize either of those technologies or you’re interested in further automating your AP processes or student enrollment, any of that type of stuff, we can definitely assist you with that more advanced automation. Victor is an absolute Brainware rock star. We can certainly assist with any and all of those needs.

One other quick thing about RPI that separates us a little bit from your standard software shop is that we are business guys. We have a little bit more management/consulting side to us as well. We really like to look at business problems as a whole and not only how we can try to make something fit into a piece of software. We have clients across multiple verticals from utilities, manufacturing, retail, healthcare, higher education, not-for-profits. Just about every industry is represented. We’re happy to present loads of references upon request. Just let us know.

I think Keith mentioned that we are here to answer questions as we go. We have well over a hundred people on this webinar. I’m going to guess that questions will come in at a pretty rapid rate. We’ll let Keith and Greg, who’s also back here, triage the questions as they come in. We’ll try to get to questions as much as we can throughout the presentation. Anything we don’t get to, we’ll be happy to follow up with you after and get you an answer to those things.

Real quick about our Imaging Strategy and Technical Services practice. When it comes to Perceptive systems, we really offer the full gambit of services. We do workflow design and implementations. If currently you’re running ImageNow for finance and you only use it for AP, we can help you do HR, contracts. We’ve been doing CapX systems. We can handle that full element for you. Obviously, as we’re here today to discuss, we perform upgrades as well as remote administration. We do have a managed services practice. We can really become your ImageNow administrators if that’s what you’d like, or we’re just here to support you however it is that you need.

We do have development staff. We can develop Custom BI reports, eForms, iScripts. We can do advanced integrations into Lawson with AGS calls, utilize web services for PeopleSoft. We’ve pretty much done it all. If we haven’t done it, we’re happy to do it. There’s really nothing too advanced for us.

We do have our own forum solution called PROFORMA. We actually had a webinar on that two hours ago. If you weren’t fortunate enough to join us, it has been recorded. That will be on our website as well, so you can definitely take a look at it there. We’re always happy to do a live demo of that for you as well. The only quick plug I’ll give to it is that it is rapidly deployed eForms. It does not utilize client-side Java, so something to think about.

The one other service that we also provide related to the ISTS group is back scanning of legacy documents. If you have filing cabinets full of HR records or full of student files, we can come in, pick them all up, take them, scan them, index them, get them loaded into your ImageNow environment. If you’d prefer, we can even scan on site. We do have a mobile operation that we can come, get it all handled for you.

Just a quick overview before I pass this off is a point of clarification. I think most are probably familiar. ImageNow and Perceptive Content are synonymous, starting with Version 7, Lexmark Enterprise Software, did begin to call ImageNow Perceptive Content. When moving to Perceptive Content, you’ve probably been made aware, it is a fairly major upgrade in terms of the database schema and some of the way the agents interact with the Perceptive Content or ImageNow server. With that being said, the user interface is not wildly different. That is not a large concern, as far as what the end users is going to see. Lexmark has announced that they will be releasing quarterly updates, which of course in the past consists of new functionality, as well as bug fixes and ongoing improvements. The present version that we’re upgrading clients to is 7.1.2. Jeff, I’ll let you go into the overview of what’s changing.

Jeff:
Thanks, Geoff. My name is Jeff Jones. I’m one of the senior consultants with RPI. I’m going to go over the next few slides discussing the changes with upgrading ImageNow to Perceptive Content 7. The release of Version 7 brought some significant changes. We’ll discuss some of the more important changes and enhancements that you’ll see when upgrading. Some of these changes are 64-bit support for the remote agents, departments and department security, folders, Business Insight. I will let Victor talk about integration server and AP eForm. While we will be discussing the changes that come with Version 7, it is important to note that much of the functionality that the organization currently has will remain the same as previous versions in the interface. As Geoff mentioned, from a user perspective does not significantly change.

We’ll get this next slide up here. Thanks, Victor. 64-bit support, I know the majority of you have long awaited 64-bit support of remote agents. We’re happy to report that beginning with Version 7, 64-bit support is here. The need for a 32-bit server is no more. Now, every organization is different. There are instances where more resource-intensive implementation should continue to use remote servers. In addition, FaxAgent still does require a physical server and 32-bit, I believe. If you are using FaxAgent, you will still need that remote server.

Departments. With 7, departments are a new feature. These allow organizations to separate or isolate business areas by department. This means security and configuration for departments such as HR, finance, can independently be managed. Departments can assign their own administrator to manage all aspects of that particular department in Perceptive Content or ImageNow. When using departments, the cross-departmental functionality requires sharing. An example would be purchasing and accounts payable, as typically there will be users that will need access to both workflows. In previous versions, all that was required was adding users to the required workflow, whereas in Version 7, since departments are isolated queues, end users that need cross-departmental access would be shared between departments.

Greg:
Jeff, that is all optional right?

Jeff:
Correct.

Keith:
If they want to stick with the default department and not set up that separate security now.

Jeff:
Correct, yeah. That sounds a little bit scary, but yeah. With the initial upgrade, everything goes into a default department and pretty much functions as it did prior to upgrading. Also, it is an additional effort to migrate solutions to use departmental security. Today, with the exception of new implementations, most customers who upgrade an existing instance of ImageNow did not utilize departmental security at the time of upgrade.

Geoff:
Certainly, it’s a good opportunity though for the larger university systems that have multiple campuses, that sometimes have multiple instances of ImageNow and maintaining separate servers, to maybe think about consolidating into a single environment that could utilize departmental security.

Jeff:
Exactly. That’s a great example of where this would be very useful. This slide here, just wanted to give a quick look at what you would see in the management console with Version 7. As you’ll see, there’s a drop-down here. If you implemented departmental security, you would have your separate departments in this drop-down. Each department would have their own set of components and security within the left pane here. Also here you’ll see the default department where, when upgrading, everything will go right into that default department and run as it was prior to upgrading.

Now, previous versions of ImageNow had the ImageNow owner, which had full administrative access over ImageNow. With Version 7, the ImageNow owner becomes the Perceptive manager. The Perceptive manager has the ability to manage cross-departmental settings, which we will see in the next slide. It has the ability to create new users, sign global permissions, create departments, and modify department labels. Another really important one is manage licenses.

Geoff:
I think one major item that they don’t have access to that in the past anyone with manager-level access could see all of the documents, right?

Jeff:
Yes, that is correct.

Geoff:
The Perceptive manager, if there were documents that are sensitive and that for one reason or another the IT department shouldn’t be seeing, this is a way around that so that they can’t actually access all documents.

Jeff:
That’s right. Here’s another slide, and this shows cross-departmental settings. When signing in as the Perceptive manager, this is probably what you would primarily see. The things to note with Version 7 is that the ImageNow server administrator is no more. Everything is done through InTool or through the management console. Here’s some examples of what you would see. Notably, sessions, which you would have seen in the server administrator prior, is now maintained in the management console. This is where you would show all your users that are connected. If you have any users that have a hung session or that are locked out, you can release them from the diagnostics menu under cross-departmental settings.

Another one to note is the license management. When using department security, you can distribute licenses across departments and manage all your licenses from within the management console.

The department manager pretty much maintains much of the admin capability as previous versions. The major difference is that when using departments, the department manager only has administrative abilities over the department they’re assigned to. They can be assigned to more than on department. In a case where you want to break out into many departments but still want to maintain some of the capabilities before, where you had a department manager that had administrative abilities over everything, you can assign a department manager to each department. They would essentially have the same permission set.

Geoff:
Jeff, it looks like we might have a couple of questions that we’re going to …

Jeff:
Yes.

Greg:
Yeah. That might be pertinent here. Are you able to sort and/or search the user sessions list in the management console back in that previous screen?

Jeff:
I believe you can search, but not sort, if I’m not mistaken.

Victor:
We’ll look at it.

Jeff:
That may be something that we could get back and give you a more definitive answer on.

Greg:
Definitely. In general, if you upgrade to departmental security, how painful is it to revert to default?

Geoff:
I think at this point in time reverting from departmental to default would be very painful.

Jeff:
Yes. I do want to point out again that initially when you upgrade, you are not upgrading to departmental security. Everything stays in that default department and functions as it did prior to upgrade. Moving to departmental security is optional, really.

Geoff:
Of course, things could then be moved back into default [crosstalk 00:15:01] theoretically.

Jeff:
We’ll talk a little bit about sharing, but the problem with that I think would be … Again, more research would be needed, but there’s a lot of things you can’t unshare.

Geoff:
I think in all reality, before you start doing departmental security a proper design needs to be in place. It’s not something to …

Jeff:
To just jump into.

Geoff:
Yeah.

Greg:
Are you able to disconnect multiple hung sessions at a time in home?

Jeff:
Yes. It is kind of difficult. I don’t believe you can do multiple hung sessions. In my experience, you’re just able to do one at a time, unfortunately.

Victor:
See if you can select multiple session and clear them out.

Jeff:
I’ve tried that before and I wasn’t able to. But that being said, it was a weird situation in this particular case I’m thinking of. Yeah, we can definitely look into that and find out more information on that.

Greg:
Geoff?

Geoff:
Yeah.

Greg:
Okay.

Jeff:
Going back to the slide here, as we see, your departmental manager maintains much of the ability to manage drawers, document types, custom properties, users and group permissions, add and remove users. This would be the last one if using departmental security, being able to share permissions across departments. This would really be the big change in their permission set.

This slide is just a quick visual on what the security looks like. You have your Perceptive manager, formerly the ImageNow owner, and then the permission sets they have. Then how it’s kind of broken out, you would have a department manager for Department A that has all of the components that they’re able to manager, and the same with Department B. Again, you could have the same department manager for each particular one if you so chose.

Another change with upgrading is the change from projects to folders, although this change was actually implemented in Version 6.7. Some of you may have already worked with folders. It’s carried over to 7.1. After upgrading, users will see a folders button instead of a projects button. On the Perceptive Content toolbar, folders would function primarily the same way from the user perspective.

The changes that come with folders are focused around content modeling, which is new to Version 7, which means folders can be assigned, drawer values can be routed through workflow. I believe Geoff had a good analogy.

Geoff:
Yeah. A good way to look at the folders is almost similar to the Windows Operating System, where you have documents that actually live within a folder. If you delete that folder, then all of the documents in that folder are deleted. Now, that being said, in Windows you can also have shortcuts to documents inside a folder, right? If you delete that folder, all you’re deleting are the shortcuts and not the documents themselves. With folders in content modeling, it works much the same. You can have a folder than actually houses the documents. Let’s say you route that folder through a workflow and at the end of the workflow you delete the folder. Well, those documents are going to be deleted also. Alternatively, you can have a folder that houses links or shortcuts to documents. Then at the end, when that folder’s deleted, those documents would continue to exist. It just adds some flexibility there.

Jeff:
Right. With the introduction of folders, index values change. In 6.6 or earlier, you had the naming convention of Drawer, Folder, Tab, Field3, Field4, Field5, et cetera. 6.7 and newer you will have Drawer, Field1, Field2, Field3, Field4. While this is not a big deal, I do want to point it out, because this is something that users would see different if you’re not renaming your index value labels. They will see Field1, Field2, Field3 as a difference. Now, these are mainly backward compatible with scripts and whatnot, with the exception of some .ini files require updating, such as Mail Agent. During the upgrade, kind of migrate over.

Now, while it’s not a major change, I did want to point out that with the upgrade of Version 7, an upgrade of Business Insight is required if you are using Business Insight. Previous versions used a package that included Cognos 8 with Business Insight. The new version has separated Business Insight out and Cognos, and both components have to be upgraded. The new version is Cognos 10. Business Insight does now use Integration Server, which we will cover here shortly.

Now, reports are no longer managed via the management console. All report creation/modification is done via Cognos. From the user perspective, again, they will still have a reports button, and they will be able to run reports from the toolbar. Again, from the user perspective, not much change. This is really more on the management side that requires Cognos use.

I’ll turn this over to Victor to discuss Integration Server.

Victor:
Hello, my name is Victor. I will talk about the Integration Server. What is Integration Server? With Version 6.7, a new agent, or a new server, was introduced. This server is a REST-based interface for Perceptive Content platform. There’s two things that come out of that interface. One, if you wanted to develop your own applications, you actually have now a way to retrieve documents, move documents through workflow. Basically, access a lot of the ImageNow functionality through a web-service-based interface.

For the second item, is it allows a lot of the agents that ImageNow actually has, or Perceptive Content actually have, to migrate to this interface as well. The new version of Mail Agent and Business Insight; actually, the new version of the Intelligent Capture Connector, those all use the REST-based calls instead of the old way of connecting to the Perceptive Content server.

Another feature that’s coming is the ImageNow Mail Agent Conversion Agent replacement. That’s coming soon, and it actually used the REST-based interface as well, the integration server. From what we’ve been seeing now, it looks like more and more agents are going to follow the same pattern, where they’re going to be communicating with ImageNow through Integration Server, instead of the old way.

AP eForm is another thing that Perceptive is constantly developing and improving. Depending on the version you’re migrating from too, they’ve improved different things. But the constant improvements are the better performance. Perceptive’s always fine-tuning how they’re doing look-ups and how much data they cache on the form. That actually helps loading time, and it helps the look-up speed for a lot of the items.

There’s always bug fixes that Perceptive’s working on. Typically things like if you click a certain button, something might not return a result, only specific conditions. They constantly tweak those and fix those.

Something was just introduced in, actually, Version 12.5, is the ability to perform live look-ups against data sources. If you wanted to, you could actually create a connector that connect dynamically to PeopleSoft, Lawson, or any other ERP, and does live look-ups instead of using the virtual tables, which are typically refreshed maybe once a day or a couple of times a day. That way, you get the live ERP data instead of having to wait for that data to refresh.

Geoff:
I’m sure lots of people will miss virtual tables greatly.

Victor:
The one thing that I do have to mention is that it does require custom development. There is an interface that is provided, but you have to basically fill in the interface to configure all of your look-ups and to actually create all of these look-ups. That’s something we’re able to assist you with.

One of the other things is a refresh button was added for the PO lines. This is specific, again, to the AP department. But previously, if you were filling out a PO invoice and you populated your PO lines, it would grab the information from the PO at that point. But if your pricing or the available quantities would change, it would never refresh that information. Right now, there’s actually a button that was added. You can hit that refresh button, and it will just refresh the quantities, add any lines if there’s any new lines on the PO, which is very useful. That way, you don’t have to clear that form and restart over fresh.

If you’re really upgrading from a really older version, 6.6 and before, previously there wasn’t really a good way to match PO lines on the eForm. If, for example, you’re using Intelligent Capture Solution and you would pool the lines from Intelligent Capture, and some of them were not paired to PO lines. Now there’s a much nicer interface, where if you have five lines on the invoice and two of those lines were not paired, you can actually select, for those two last lines, what PO line they belong to. It’s a much cleaner and nicer interface. It’s been around for a couple of versions. I’ve worked with a couple of customers recently that have not had that functionality yet.

Geoff:
Let’s talk about some of the challenges.

Jeff:
Yeah, so I’ll step in and talk about some of the challenges. We’ve done a number of these upgrades to 7.1 from both 6.7, 6.6., and 6.5, even. These are the major ones that we’ve seen–

Jeff:
These are some of the major challenges that we have seen. First of all, initially you could just go straight from 6.6 to 6.7, but there were quite a few issues that arose from that. So Perceptive came back and said, “You need to go to 6.7 first from your current version, then go from 6.7 to 7.1.” Now, while this is a lot cleaner, there are some items that don’t commit when running the incremental database scripts in a utility. You have to manually run these utilities to finalize the upgrade.

Some scripts may need updating. Now, much of this, we can look at most of the scripts and pinpoint if there’s some that we definitely need to update. Typically, during testing is when we encounter any errors, and then we can fix them along the way.

For those of you using eForms, the .xsl and .xml files have a encoding line, and there needs to be an update of each .xml and .xsl file with this line here, basically, to just update it to the UTF 8 for them to work properly. If not, they won’t open half the time, or just throw a lot of errors.

Geoff:
Having been some of the very first people ever to perform these upgrades, let me tell you how fun it was to figure that one out.

Jeff:
Yes, this was not something that was documented at the time.

Now, some components require manual migration and configuration. We mentioned this before. Mail Agent is one. With the new Mail Agent and Integration Server, Mail Agent’s kind of a separate install. It doesn’t upgrade the previous Mail Agent. We really just uninstall Mail Agent, install the new version, and then we have to migrate the settings over. But that being said, if you’re coming from 6.6, we do have to upgrade Mail Agent to 6.7 to get the newer configuration lines.

Then there’s database changes. 7.1 is bigger. It’s got a bigger database. With all these changes, it may require more resources to run efficiently. We can evaluate your system, take a look, and make suggestions on what we feel is a good start.

Geoff:
What kind of questions do we have?

Greg:
A variety here. I think you just covered something here, and there’s a specific aspect to it. Will iScripts need to be rewritten when upgrading to 7? For example, scripts that automatically create projects. It’s probably going to depend, but …

Jeff:
It depends on the age of the script. Again, there’s a lot of backward compatibility there. I have encountered scripts that do autocreate projects that we have not had to upgrade at all. Then there are some that we have. Again, we initially catch that during testing and then upgrade as needed.

Geoff:
I think one way that we’ve been able to do just a real quick litmus test would be to take a look at those iScripts and see if they’re utilizing the STL packages.

Jeff:
Yeah.

Geoff:
If they’re older than STL packages existed, then there’s generally a good chance that they’ll need to be modified. If they are using the STL packages, I’m not saying they won’t need to be modified, but there’s a much better chance that they won’t need to be modified.

Victor:
Most of these upgrades, you’re never rewriting the iScripts from scratch. You might have to modify a couple of lines of script to specify either the department that the document needs to go or the folder it needs to be created in. But, again, you’re never starting from scratch and rewriting the whole iScript. It’s minor tweaks, typically.

Greg:
Okay. Not sure if we’ll know the answer to this, but the whole two-step upgrade, I believe this is referring to, would this be expected if we wait to go to Version 7.2? In other words, instead of upgrading to 6.7 and 7.1, do you know if we’re going to have to then either go to 6.7 then 7.2, or go to 6.7, 7.1, 7.2?

Jeff:
I can’t definitively say, but I’m going to say, yes, it would still be required. Again, like I said, from 6.6, when 7.1 first came out, we suggested upgrade directly from 6.6 to 7.1. But it just was never clean. I don’t know if it’s just the incremental scripts just weren’t committing everything correctly. There’s a lot of these, they call them ‘Ion upgrade util┬ácommands’ that run. A lot of times, they weren’t just running and committing to the database correctly.

When Perceptive came out with the new two-step process, we did that, and it did clean it up quite a bit. We still have to run, like I said, some manual stuff. But I’m going to say, since we don’t see the new framework and schema until 6.7, I would say that even with 7.2 we probably will still have to do a two-step process.

Greg:
Okay. I’m going to have to ad lib here a little bit and make a little disclaimer, because we’re getting a lot of questions on version sun-setting paths and so forth. Well, I’ll let Geoff make a little disclaimer here that we are not Perceptive, we are not Lexmark.

Geoff:
Yeah, we are not Lexmark Enterprise Software. We don’t represent Lexmark or Perceptive. In terms of the versions, all of that, we really can’t speak to it. I can say that there is a document on the customer portal. If you, I think, just do a search for “end of life,” I want to say, that document will come up. Or if you’d like to email us after the fact, if you hit the next button, will get my business card. Feel free to email me. I’d be more than happy to send that document to you as well. In terms of anything licensing or version sun-setting, we can’t really tell you too definitively.

Jeff:
Do we know what the official end of life for 6.7 is?

Geoff:
6.7 ends life, I believe, in 2017. It hits limited support next year. 6.6, on the other hand, does hit end of life in three weeks, or whatever. January 1st is end of life for 6.6.

Greg:
Do you have the commentary on what limited support means for 6.7, just what our experiences have been?

Geoff:
Yeah, so our experience has been that Perceptive will support it. At the time that it hits end of life, generally, Perceptive really won’t support it. What we’ve been seeing from some clients is Perceptive offering an additional fee to support. Generally, with the limited support period, what that means is that they’ll support it to an extent. But if any patches are required, which oftentimes there are for issues, they will not release any patches.

Victor:
They’ll release the patch for the later version. If you’re on 6.6, they might fix it in 6.7, but they won’t make it backwards compatible.

Geoff:
Just re-disclaimer, this is opinion, not fact.

Greg:
Right. I think this fits under that category as well. Can you give me some additional details on the INMAC replacement and when it will be released? I don’t know what you’ve heard, whatever you’re comfortable sharing.

Victor:
I’ve seen it exists. It’s really slick. It’s really fast. I don’t know what the official timeline for that release product is. It is coming. I know that much. Maybe Inspire will be announced, hopefully.

Jeff:
Yeah. Yeah, I think it’s big enough, they might talk about Inspire, yeah.

Victor:
Yeah.

Greg:
Understood. Has the Oracle DB performance been addressed in ImageNow 7.0-plus? I guess, are you guys aware of some known Oracle Database issues?

Jeff:
There’s a lot of bugs throughout versions. There’s a lot of fixes. I’m not personally aware of a DB issue. It’s definitely something that we’d be happy to look into and see.

Geoff:
There have been lots of clients that run Oracle, of course. It might be, that might be something version specific.

Jeff:
Could be, yeah.

Greg:
Okay. Feel free to follow up with some questions on that.

Geoff:
Yep.

Greg:
I guess kind of the reverse of a previous question. The painful one, if you wanted to revert back from departmental, what if you upgrade with the default settings? Can we later change to the departmental settings?

Jeff:
Yes.

Greg:
Yes.

Jeff:
Yes, you can later. Again, and I think he mentioned this, that would be a situation where we would definitely want to sit down and work out a design, to really make sure that we have an understanding of where you want to go with this when you go into departmental structure. But, yes, you can move into a departmental structure. It’s kind of the intention down the road.

Victor:
I think we’ve mentioned this before, but when you upgrade, by default everything is in the default department.

Jeff:
Right.

Geoff:
There, yeah.

Victor:
All the security settings that you had before, your HR is going to be separate from your AP. That’s probably controlled more at the drawer level, and that’s going to stay exactly the same as it is today. What will not happen automatically is your HR drawers and everything else is not going to move into the HR department until you set that up and you actually migrate all that configuration over.

Geoff:
You’re doing it after the fact is what it pretty much comes down to.

Victor:
Yeah.

Greg:
Can there be more than one manager?

Jeff:
There can be more than one manager. Again, department manager, that role hasn’t changed too much. Yes, there can be more than one. You can promote. It’s the same thing. I keep wanting to say, “ImageNow.” Your Perceptive manager is responsible for promoting users. When promoting users, you’re basically promoting to manager. Yeah, one department can have multiple managers.

Victor:
I think this is more of a question. You can have multiple department managers. But then Perceptive managers, I’ll have to look it up.

Jeff:
No, Perceptive manager is Perceptive manager, just like owner. You can have one owner, one Perceptive manager.

Victor:
All right.

Greg:
I don’t know if you’re going to know this off the top of your head. What are the database requirements, version resources necessary, et cetera?

Geoff:
Come on, let’s go.

Victor:
Docs.PerceptiveSoftware.com. Click ImageNow, or content …

Geoff:
Requirements.

Victor:
… There’s a technical requirements document. We can send out the link after the webinar.

Geoff:
Send us an email once again, and we can send you out that document or a link to that document.

Jeff:
It’ll have technical information for everything.

Greg:
Any big changes to the import agents?

Jeff:
I could be wrong here. I think in 6.7 they did introduce the Capture Profile import agent.

Geoff:
6.6.

Jeff:
Was it? Okay, so 6.6, so most of you have already seen that. Outside of that, no, there’s really no changes that I can think of off the top of my head, no.

Victor:
All of your existing import profiles should work.

Jeff:
Yes.

Greg:
All right. Is there a utility available to update the .xml encoding to UTF 8, or can this be done using a third-party tool, such as Notepad++?

Geoff:
Yeah.

Jeff:
Yeah, it’s all manual. Yeah, there is no utility, unfortunately, that I know of yet.

Victor:
Notepad++ will work though.

Jeff:
Yes, that’s how we normally do it.

Victor:
Yeah. It’s not a crazy amount of files. It depends on how many forms you have.

Jeff:
Right.

Victor:
But you don’t have to … The .xml data itself that’s stored in the .osm files, you don’t have to go back and update all of those files. You just have to update the configuration files only.

Jeff:
Yeah, and then Server 6 directory, forms or worksheet, whichever one you’re using, yeah.

Victor:
Yep.

Greg:
The question was clarified that she was asking about multiple Perceptive managers. I don’t know. I was reading along. Did you answer that?

Jeff:
Yeah, Perceptive manager is just one. Just like before, where you could have one owner, yeah. All they did was change it to call it Perceptive manager, and then they limited the permission set that they had with it.

Victor:
I can speak real quick. The whole goal of this migrating to Perceptive manager versus department manager was to separate more of an IT role versus more of business analyst that’s actually working directly with that department. Typically, your Perceptive manager will not go in and try to change your user security for a particular user. That’s something that a department manager would do. Typically, one Perceptive manager does the bulk of the work.

Jeff:
Yeah. Ideally, I think it’s just getting each department to manage their department.

Victor:
Yep.

Greg:
Is the Integration Server required for Cognos?

Jeff:
For BI, yes. For Business Insight, yes. If you’re using Business Insight, it is required.

Geoff:
I would say, because I know that we get this question all the time, and again with my disclaimer that we can’t really say anything official about licensing, but my understanding from what we’ve seen is that Integration Server, as long as it’s used with the core Perceptive agent, does not require a separate license. That’s included with your content server. You only need to buy the transaction package if you’re utilizing it to integrate with third-party applications.

Greg:
Okay. Are there any changes to the Forms Designer?

Victor:
I can’t say that I’ve looked at it in 7.1.

Jeff:
Most people didn’t really use the Forms Designer much before.

Geoff:
The Forms Designer isn’t something I’ve ever seen used outside of just creating a blank form to then code the .xsl with. Probably not something we …

Jeff:
I can’t say that there’s any major changes to that. We can definitely look into that further, but I don’t think so.

Greg:
Okay. Here we have a panel question. Thoughts on doing a clean install of 7.1 versus upgrading? Have we thought through that?

Geoff:
Yeah, this has actually come up lately. I think that what this stems from are from organizations that have been utilizing ImageNow for an extremely long time and maybe are concerned that, along the way, there’s been some level of corruption in the database or just various issues that have been introduced that, in the past, just haven’t been addressed. The concept is possibly, rather than doing an upgrade, actually clean installing 7.1 on a new environment and then migrating the documents and configurations over to that.

Can you do that? Yes, absolutely. But one of the big caveats to that, that you can’t just migrate the documents. There is no way to simply say, “Okay, we’re going to drag this part of the database over.” The documents are purposefully encrypted within the .osm, as to how they’re stored. What is means is that you have to actually export all of the documents out and then import them into the new environment.

We have done that in the past. We have scripts. It’s doable. Then there’s one more caveat to that, which is if you’re utilizing annotations, the only way to get those annotations out with the document is to own output agent licenses. Output agent licenses are throttled. It might mean needing to ask Lexmark if you can have some temporary output agent licenses as well. Who knows? They might just give it to you for free. Do you have chronic problems that you’re trying to fix? But it is an undertaking and would be, I think, very environment specific as to what the level of effort would be.

Jeff:
The other side of that too, and correct me if I’m wrong, is that most of what you see in ImageNow is stored in the database. That probably would require rebuilding workflows manually. Pretty much anything, recreating drawers, everything, would have to be recreated, versus just migrated over. It would be a true new implementation, yeah.

Greg:
Right. Depending on your complexity and your situation, it might make more sense. Obviously, also, the challenges that you’re having. Can reports be built using the ImageNow views? In other words, can search view be turned into a report? Any creative ideas on that?

Jeff:
Oh, man, I was just reading about this the other day. I’ll have to verify this. I believe they might have removed the ability to create a report based on view in 7.1. I think they did.

Geoff:
Previously, the reports, that was done out of the management console.

Jeff:
Yeah.

Geoff:
With BI being removed from the management console …

Jeff:
They’ve taken that away.

Geoff:
I want to say that that’s taken away. But we could verify that and follow up.

Jeff:
Yeah.

Greg:
A previous question was actually on that. Is report security no longer done through the management console? That’s correct, right? I’m going to try to paraphrase this. Is WebNow a pure HTML client, or is Java still used, based on an applet, in content 7?

Geoff:
It has not changed.

Jeff:
WebNow has not changed.

Victor:
It’s still Java based.

Greg:
We’re still going to have problems with Chrome?

Geoff:
Correct. Until …

Jeff:
I don’t know when that’s going to happen.

Geoff:
Yeah.

Jeff:
I know where they’re going with that, but …

Geoff:
For two years now, it’s been imminent. I don’t think I want to comment on when that will potentially be.

Victor:
There’s progress being made. There’s a couple of apps that have been released that are HTML5, full HTML application, one of them being the invoice-approval app. They’ve demoed it at the Inspire. Basically, that one is designed for nothing but if you have a task-based AP approval workflow, your approvers can actually log in through this new app that they built and actually approve invoices there. It’s a full HTML5 application. That’s the only one that I know of that’s released just to be HTML5. It’s very specific. It has very specific requirements for it.

Greg:
Okay. We’re pretty much actually out of questions here, but I’m going to give a minute or two. I didn’t give the warning before, so if anybody wants to type in any more questions or feel free to yell at me if I missed your question, retype it please.

Okay. I did have one just come through. We currently have .osms on the same server as the program. What challenges to move those to a separate SQL server?

Jeff:
You wouldn’t move the .osms to a SQL server. Really, with .osms, it’s just a matter of copying the .osms, moving them to a storage that you want them on, and then we just update the pointers in Perceptive Content to point to the new location. It’s not a major effort.

Geoff:
That’s, again, something that if you email us about, we can send you some information. We’d be happy to spend a few minutes.

Greg:
Okay. Is there a ballpark percentage of how much additional data space would be required on the server, on 7.1 versus 6.7? Any …

Geoff:
I don’t believe it requires anything additional.

Jeff:
Yeah, I don’t think so.

Victor:
It might, actually, require additional. There’s new tables and new things introduced. I don’t know if we have the ballpark number. It also changes because the columns added to different tables. If you’re using projects more than documents, or you have more custom properties than you have something else, there’s probably different requirements for that. You can always run the upgrade. You can take a copy of your database, run the upgrade scripts, which are actually just SQL code. Once you run those upgrade scripts, you can see what the difference is in the database sizing. Those should be fairly easy for your DBA to run. Again, as long as you’re working with a copy, just don’t run it in production by itself. Take a copy of that whole INL6 database, run the scripts, and you’ll be able to tell pretty quickly.

Greg:
Okay. Would screens need to be relearned to be captured?

Jeff:
On most upgrades that we’ve gone through, the only time we’ve really had to relearn anything is if we’re going to a newer version of, say, IE. Typically, when we upgrade, so far, nothing has needed to be relearned. Now, that doesn’t mean that it won’t. As we said, that’s just current experience. But as of right now, I have not seen any that have to be relearned.

Greg:
All right. We’re back to the clean environment. How about installing a clean environment, moving from Server 2008 to 2012, and then upgrading the database with the SQL scripts?

Jeff:
That’s actually how we would typically do it.

Geoff:
Yeah, that would be our standard. Generally, our approach is if you have a new 2012 box and you’re going from 6.6, we would install 6.6 on the new 2012 box. We’d replicate your existing production environment from your 2008 box to your new 2012 box. Upgrade that 2012 box, perform testing, make script modifications, perform UAT, and then actually replicate that to another 2012 box that would then become the test environment. I’m sure that was very difficult to follow, but, yes.

Greg:
It sounds like you’ve never done it before. Which leads me to another question here. How many successful upgrades has RPI completed from 6.7 to 7.1?

Geoff:
We’ve got over 10 at this point. Not necessarily exactly 6.7, but between 6.6 and 6.7.

Jeff:
And one 6.5.

Geoff:
And a 6.5, and soon to be a 6.4.

Greg:
What are the biggest changes, from a user perspective, from 6.6 to 7.1? That is, how much relearning is expected from end users?

Jeff:
We discussed that a little bit. Yeah, there’s really not a lot. Again, the biggest thing the users are going to see differently is the changes from projects to folders. On that Perceptive Content ImageNow toolbar, instead of seeing projects, they’ll see a folders button. Then the changes in the index values, Drawer, Field1, Field2, Field3, instead of Folder tab and whatnot, is really the biggest changes. I don’t think there’s really much else that they’re going to see differently. I would say there’s very minimal retraining, if at all, from the user side.

Victor:
Every time I’ve done upgrades so far, you don’t have to retrain the users. We can upgrade the environment in place. The toolbar stays the same. Documents, views, old searches, everything stays pretty much the same. A lot of changes happen under the hood in the system. As far as the user experience, there’s no drastic changes.

Greg:
Okay. Can the 6.6 client and the 7.1 client be installed on the same desktop?

Jeff:
No. In any version, that’s always been the case. You can’t have two different versions of the client installed on the same PC.

Geoff:
If you’re running a Citrix farm, you could potentially run one in the Citrix farm. But otherwise, no.

Greg:
This might be very specific, but who knows, maybe you’ve run into it. Do you know if a different fax card has to be installed to be compatible with the 2012 R2 server? We are currently running version 6.6. We usually don’t get into …

Jeff:
Yeah, we really don’t. I don’t think there’s a new card involved. That’s 2012 specific. I don’t know, yeah.

Victor:
Yeah, I think that’s something we can look at. There are specific requirements. Fax Agent is really the only one that has really specific hardware requirements. There’s not a lot of customers that do use the Fax Agent itself. But we can send out the Fax Agent documentation. It’s actually on the Perceptive website. It is documented fairly well, as far as what the requirements are. We can send that out.

Geoff:
Almost all of our clients have moved to a system where, instead of using Fax Agent, they just use some sort of e-fax software that then sends the faxes through Mail Agent. But certainly something we could look at for you.

Greg:
Okay. It looks like somebody else has some fax card issues as well. Maybe we’ll get some knowledge sharing going here. Any special updates or changes that need to be done for the scan stations, the ones using Kofax? I guess we’re talking Kofax VRS, but correct me if I’m wrong.

Jeff:
I just had an update with Kofax and had this question. We went to Perceptive to find out specifically. We were told that no updates were needed for the VRS side with 7.1. This is coming from 6.6. Again, that would be definitely something we would want to get a definitive answer on. We could find out for you.

Geoff:
We haven’t seen that so far with any of our … No.

Greg:
Well, we are just about out of questions. More just popped in here. Anybody else, please get them in. If I can’t install the 6.6 and 7.1 clients together, what is the recommended method for testing and/or training before a live migration?

Geoff:
You need to have test machines. Test machines or …

Jeff:
Citrix.

Geoff:
… A Citrix farm.

Greg:
I think with that, any final comments?

Geoff:
No. Thank you very much. Again, my information is up here. If you have any questions at all, please feel free to email me or give me a call. It sounds like a lot of you might be interested in faxing me. I have that information there as well. Other than that, no, thank you very much for your time. Have a great rest of the week.

Jeff:
All right. Thank you very much, guys.

Victor:
Thank you.

Greg:
Thanks, everyone, for attending.