Creative Uses for Perceptive iScripts and eForms

RPI has been consulting on Perceptive Content so long we remember when it was Lexmark Enterprise Software, and ImageNow before that. In that time, we’ve seen a lot of solutions using iScripts and eForms – some that were really creative and great (and some not so great).

Either way, these custom development solutions can automate many manual processes and tasks, making your Perceptive Content solution more effective for end users and your IT department. In this webinar, Senior Solutions Architect Alex Lindsey and Lead Consultant Michael Madsen will share some of our favorite – and not so favorite – Perceptive iScripts and eForms.

Download PDF

Michael Madsen:
Hello everyone and welcome to another Webinar Wednesday. Today we’ll be talking about iScripts and eForms. Before we get started, a few housekeeping items. This webinar will be recorded and will be posted to our website and on YouTube, and the deck will be available later this week. You can view this recording and all of our previous recorded webinars on, then you can also please submit ideas for other webinars you’d like to see. We’re always apt to get those.

So we have another upcoming webinar today. Oh no, I’m sorry, these are for the December 5th webinars. We have AP automation with Kofax TotalAgility,  Lawson APIA at 11:00 a.m. and then content management with Infor Lawson at 1:00 p.m. central.

Alex Lindsey:
Sure thing. To introduce ourselves a little bit before we start talking about the iScripts and eForm solutions, my name is Alex Lindsey. I’m a Senior Solution Architect with RPI Consultants. I’ve been working with the Perceptive Suite for quite a long time as well as some of the supplementary OCR technologies that go with it, specializing in just weird solutions and accounts payable mostly. I’m also a novice axe thrower.

Michael Madsen:
And hello, my name is Michael Madsen. I’m a Lead Consultant at RPI. I have extensive experience scoping and designing custom solutions for the higher education space, accounts payable and also manufacturing. I am a bad movie connoisseur. Oh, hi Mark.

Alex Lindsey:
Yes. So a little bit on the agenda today, we’re going to start out by talking about ourselves again. We’re going to jump right into kind of an overview of what Perceptive Content iScripts and eForms is, we’ll cover a few creative solutions for use you can use iScripts to help your solutions out, and we’ll cover some more of the non-standard eForm solutions that you might see, and then we’ll open up for questions.

A little bit on RPI Consultants, we are a services firm. We have over 80 full time consultants, project managers, technical resources, people that are much smarter than myself working across several offices in Baltimore, Tampa, and right here in Kansas City. We offer a range of services from design work, to managed services, basically run the gamut of what you need to do for your software suite. The softwares that we do work with and we are partnered with are Kofax, Infor, and Hyland as well.

Michael Madsen:
So what we’re going to start with if Perceptive Content iScripts, and then what we’ll do is move over to the eForms overview.

For Perceptive iScripts, the thing to know about Perceptive iScripts is that really they’re just Javascript scripts, but they’re specific to Perceptive/ImageNow. They can be defined with multiple triggers, so you can set up an iScript to be an inbound or outbound action inside of workflow. You can also use a BAT file to set them up with a scheduled task.

Some general uses for iScripts would just be like automated routing, external lookups and queries. So if you want a query against an ERP database or an external source, we can set that up inside of iScript. Custom data manipulation, so if we had a date field on a form and we wanted to put together a standard format for that field, we could utilize custom data manipulation for that to massage the value to make it look how we want it to look.

Also, automated notifications. A lot of people have clerks that put together emails and send them out. That’s a lot of stuff that we can automate. We don’t need people to type out these emails every single time, so you can create iScripts that send out these notifications so you don’t have to write them. Finally, one thing to note about iScripts is that there is a vast library, it’s called the STL. This is the library that Perceptive has put together for us to use with iScripts, so there are a lot of functions that are already available for us to use. We just need to tap into the STL to add into our script.

Alex Lindsey:
Perceptive eForms is just a general overview. Some of you may have eForms already within your Perceptive Solutions, but essentially it is a user interface that allows you to store additional metadata to do look ups, to do validations, the most common one for a lot of your customers is the APE form, which we’ll touch on in a little bit. With any eForm, whether it’s a standard or product eForm, we can add a lot of just general customizations to it, or validations essentially, like Mike was mentioning field validation is required, character length, things like that.

It’s great for lookups. That what we generally use eForm data for. If you have a workflow solution or a workflow process that’s in place or not in place right now, you can basically use an eForm to store metadata or have users input certain things to basically process them through. Again, they’ll do look ups just like iScripts do.

There are several ways to deploy forms. There’s basically custom forms, there’s also product forms. But custom eForms that can be built within the Perceptive Suite to store data, these can be as basic or complex as you need them to be. You can have buttons that can do certain things, or trigger other actions and things like that. There’s also Forms Server and Yoga Forms. Forms Server and Yoga Forms, they’re slightly similar. But essentially, if you have a submission process in place, there’s a site set up where your users can kick off a process, input the data, attach documents, supporting documents and then push that into Perceptive to basically kick off a workflow process, or just archive it and store it.

Michael Madsen:
What we’re going to go start with is some Creative Solutions Using Perceptive iScript. If we talk about iScript, we can talk about iScript all day long. We thought the best way to approach this would just be to go into a few solutions that we put together using iScript for some of our customers.

The first example is an accrual report merge. The problem that a customer had was they were generating an accrual report inside of Perceptive content, but then also creating their own manual report through a different process outside of content. Some of the data may be similar, but they’re also pulled from different areas, so they wanted a way to merge these reports together so that they had a complete report that showed their true accrual. What we did to do that was we can utilize CLIB, the CLIB library inside of iScript, to read the CSV files that they were generating through these reports.

When we read those reports into iScript, we can then loop through the lines on each of those reports to compare the lines to each other. If we find duplicates, then we wipe that out. Then we take all of the unique lines, loop through every item inside of the unique line, and then match the company value to determine totals at the end because another thing that they wanted to add to that report was a summary total list at the bottom of the report. So using those functions, we’re able to generate our final report.

Alex Lindsey:
That’s extremely important for accruals, especially if you’re monitoring specific accounts. If you had a corporate account that you know can’t go over a certain threshold, you can add that total to the bottom and you kind of keep a closer eye on the accounts that you’re charging your invoices against.

Michael Madsen:
Another example is tax form imports. We have a customer who would generate their tax forms in a batch, so they would get one single PDF that was a multi-page PDF. But each page was dedicated to an individual employee. What we needed to do was split those PDFs out so that we could actually link them into the employee folder. Keep in mind that when you’re working with iScript, you aren’t barred to just using iScript. You can really think out of the box and do things outside of iScript before it hits the script.

In this example, what we did is we actually utilized Ghostscript as its own process before hitting the iScript. We can use Ghostscript to not only split out the PDF pages into their own files, but we can even create text files that contain the data within that PDF that we can read through using iScript. So essentially what we did is we split those out, created an index file to go along with the individual pages, and then through iScript w