Is It Time to Take Your Workflow In For a Checkup?

Almost every business has documents that go through some kind of work process such as expense reports and application processing that uses some kind of Business Process Management [BPM].  BPM is generally defined as a systematic approach to improving and automating an organization’s business processes and workflows.  These workflows may be core to your business process and over the years as rules, regulation, and other external factors alter the original flow it is critical to to plan on performing regularly scheduled checkups of your BPM processes.

While supporting systems that have little or no changes to their BPM workflow maps in over a decade it is very common to run into issues and complications caused by knowledge workers who have devised workarounds for changes that have occurred over time.  One of the biggest problems I see with not revisiting and performing analysis and research to get a current picture on a regular basis is User Acceptance.

When we run into this type of a situation the knowledge workers are often frustrated and highly irritated with the software and how the system works.  The user feels that their performance is based on rules and regulations that no longer apply and will complain stating “I had nothing to do with how this was configured”, “this is how we do it because it has always been like this” and “I don’t understand why we have to do it this way.”  The user is often very negative about the inefficiencies and wants to tell everyone and anyone willing to listen.  This can have an immense impact on the work environment and acceptance of your ECM system and future applications.

Where to start:  The efficient flow of documents through your organization is critical to remaining competitive and document management and workflow solutions are proven to cut cost and improve efficiencies.  If you have been using a rules based electronic workflow for over 3-5 years it is a good practice to review the “as is” state of the workflows and update them on a regular basis.  BPM workflow updates should be visible to upper management and budgeted for the future along with software upgrades.  Most importantly involve the knowledge works in the discovery and development process. “Because we have always done it this way” does not need to be the number one comment about your ECM system.  The success of BPM is rooted in starting with the right process and continuing best practices for regular checkups and maintenance.

Leigh Woody

Program Manager

ImageSource, Inc.

ILINX Capture: Scanning in a Production Environment

ILINX Capture utilizes a web based platform that combines functionality as well as ease of use while scanning in a production environment.  This platform allows production workers to remotely tap into the system to perform any task in the production workflow.  Capture makes use of many different image enhancement techniques.  In ILINX Capture’s production environment, batches move through the processes in an efficient and organized workflow. 

ILINX Capture’s web based platform makes it possible for a technician to scan and process batches from remote locations.  This feature allows technicians convenient access to the production environment while not at the same locations.  Each process in the workflow (ie Capture, Classify and Indexing) can be performed by an operator whether or not they are on site.  Knowledge workers can answer questions without having to look over the shoulder of the production worker. 

ILINX Capture has many functional image enhancement tools for scanning less than good quality paper.  Images can be replaced, inserted or appended at any stage in the workflow process.  Images can be copied into various places throughout the batch.  Images can also be printed at anytime during the workflow.  If images are scanned out of order and need to be corrected, with ILINX Capture you can move images around after they scanned into the system. 

The most important aspect of Production Scanning is efficient workflow.  ILINX Capture workflow allows batches to move seamlessly from one process to the next.  Batches can also be moved backwards in the workflow if they need to be reworked.  With ILINX Capture you can use any scanner as long as the PC you are using has the twain drivers installed on it.  In the user window, a batch can be easily found at any stage in the workflow without confusion or the necessity of using the Server Manager.

Jeff Martin                               Ali Adam

ImageSource, Inc.                ImageSource, Inc.

Barcode Document Separation with ILINX Capture

While exploring different document separation techniques I discovered that bar code separation may cause the document to be split multiple times.   I scanned in a single document that had 334 pages and for some reason it split the document multiple times.  There were no other barcodes except one Patch Type T separator at the beginning of the document.  

After looking over the settings on the Barcode QSX module inside the ILINX Capture Server Manager I noticed that the Patch Type T document separator and the 3 of 9 barcode separator were enabled.  Please see picture below…  

ILINX Capture Barcode OSX Module

One of the challenges with setting up barcode separation with both Patch Type T document separator and the 3 of 9 barcode separator is that every time the recognition engine comes across a 3 of 9 barcode it will separate the document automatically regardless if you want it to or not . Unfortunately the software can get tripped up on its own logic and every time the recognition engine comes across a 3 of 9 barcode it will separate the document automatically.  ILINX Capture’s recognition engine still separates by the Patch Type T Patch Code as well as every 3 of 9 barcode. This can give unexpected results with the number of documents that are automatically generated.  To fix the above example I removed the bar code separation because it was not needed. As you can see in the following example…  

ILINX Capture Barcode Settings

However, in some cases this may not meet a client’s needs and different approach to document separation is needed. The best practice for multiple document separation is when using Patch Type T Patch separator pages and 3 of 9 barcode separation you need to add a prefix for each type of document you want to separate.  

Here is a good example:  

A client may want to separate documents by what’s in the barcode itself, such as capturing the word “ILINX” in the barcode for a document type of “Application” and the word “Invoice” in the barcode for a document type of “Invoice”.  To do this you need to add a prefix value with a document type see.

As you can see ILINX Capture has the ability to be customized to fit your needs no matter how basic and/or how complicated the requirements are. The main concept here is ILINX Capture is a very powerful tool and needs to be configure properly to get want you need out of it. The above example is only a small scratch on the surface on what this tool can actually do.  

However, in some cases this may not meet a client’s needs and different approach to document separation is needed. The best practice for multiple document separation is when using Patch Type T Patch separator pages and 3 of 9 barcode separation you need to add a prefix for each type of document you want to separate. 

A client may want to separate documents by what’s in the barcode itself, such as capturing the word “ILINX” in the barcode for a document type of “Application” and the word “Invoice” in the barcode for a document type of “Invoice”. To do this you need to add a prefix value with a document type see.

ILINX Capture Prefix Settings

As you can see ILINX Capture has the ability to be customized to fit your needs no matter how basic and/or how complicated the requirements are. The main concept here is ILINX Capture is a very powerful tool and needs to be configure properly to get want you need out of it. The above example is only a small scratch on the surface on what this tool can actually do. 

John Hart
ImageSource Inc.

  

How To Perform Basic Web Troubleshooting for IPM Web

Web troubleshooting can be difficult and searching through Oracle Metalink to get information can be even worse.   I found this record in the Oracle Archives and thought it may help out other Acorde/Stellent/Oracle IPM/UCM users.  The following is a general guide for troubleshooting issues with the IPM Web service.  Hopefully reviewing the installation checklist and going through this troubleshooting guide will resolve most configuration issues with the web service.

Solution

Installation Phase

This phase encompasses all steps outlined in the install doc. If problems occur during or immediately following the installation, please review these steps:

1. How was the installation done?

At the console or through terminal services?

Terminal services has been known to cause serious issues in our installation of the web. It appears that when the install is done in this way, some files are not registered properly. Typically, you will see errors pointing to COM (login errors, plugin errors, etc.).

2. Were all the installation steps followed?

Check permissions, and verify that objects under the IBPMWeb and IBPMData folder all have the correct permissions. Reset all child objects under IBPMWeb and IBPMData. Make sure the correct web extensions are enabled.

3. Has the current problem been happening since the system was installed?

If yes, then you may need to review the install documentation.

4. Check the HKLM/Software/Optika/TRANSPORT/MANAGER_ADDRS

Make sure it points to the actual Request Broker machine (either the hostname or IP address). Also make sure the webserver can ping that address or hostname.

5. Is there a client or other services installed on the webserver?

If so, please understand that this is not a recommended configuration. In the event it is unavoidable, make sure that the services, (client and web) are all installed into the same location. For IPM web, the DLLs should be installed into C:\Program Files\Stellent\IBPM.

Startup Phase

This phase encompasses the process after installation or after an IISRESET.

1. Do the clients get the login screen?

If not, then we’re failing prior to getting all the ASP\DLLs loaded. Typically this points to either a permissions issue or a corruption in the IBPMWeb\OTInfrastructure\AcordeObjectHeaders folder. Delete all the files in that folder and do an IISRESET from a command prompt.

2. Can the user successfully login?

If not, this means that we are not getting a COM connection open to validate the user. Typically we will see a 29515 error appear stating we were not able to reach a service. In this case look at the permissions on the HKLM\Software\Optika registry key. Another item to look at is to make sure that if for some reason we have a client on the webserver that it is installed into the same folder as the IBPMWeb. Installing elsewhere will cause the web problems when it goes to register DLLs.

3. Is the error in the workcenter or elsewhere?

If after login we see an error on the workcenter, this points to an issue with the AcordeObjectHeaders folder. Rebuild that directory.

If the error happens in another window or frame then we’ll need to investigate those individually.

4. Is the client machine following a shortcut that points to a file below IBPMWeb?

In the past we have seen issues where a client will follow a shortcut that they created when at the login screen of the IPM Web. Doing so causes certain startup processes to be bypassed and can cause problems later because they may be using outdated connection information or other bad data that can cause varied problems.

Post Startup Phase

This phase encompasses any issues that occur after a successful installation and login. These errors typically come from problems with COM or from the connection to the backend servers. If these errors occur after an upgrade to the OS then check to make sure that any firewall or antivirus changes have been deactivated temporarily until we can determine if one of them is the cause.

Plug-in related Problems

For issues related to the plugin, look at the following:

1. Does the Messenger virtual directory contain an ISAPIMsgr.dll?

If not, then the Messenger virtual directory is pointed to the wrong location. Delete and re-create the Messenger virtual directory and point it at C:\Program Files\Stellent\IBPM

2. Does IUSR/IWAM have full control to the IBPMData folder?

If not, correct the security settings and then reset all child objects on that directory.

3. Are the users accessing the web with the hostname or IP address?

If they are using the hostname, you may want to adjust the Web Settings so that it uses hostname over IP (Login with a Web Administrator, click Administration -> Choose Web Settings -> Change the first section to use hostname and specify hostname.domain.com in the text box->Save the settings.)

4. Is there a proxy between the clients and the webserver?

If so, use the explanation for #3 and change the setting to hostname.

5. Are we seeing a *.opt file get created in the IBPMData\IBPMSessionData\<sessionid> folder?

If so, is the file larger than 4k? If so, open the file in a test editor and see what the message is. If it is larger than 4k we can assume that the images are getting to the webserver from export. This would indicate an issue with the plugin loading the image from IBPMData.

6. Check the IIS log and see if ISAPIMsgr.dll is listed as being accessed.

The log can be found at C:\Windows(orWINNT)\System32\LogFiles\W3SVC(number of website)\ and will be named after the date in which it was created. This file is helpful in troubleshooting different problems when you need to see if certain items are being requested from the web server.

How to do a complete uninstall of the IPM Web:

1. Use Add/Remove Programs to uninstall the web

2. Delete the Program Files\Stellent folder

3. Open Regedit and delete HKLM\Software\Optika and HKEY_CURRENT_USER\Software\Optika

4. Remove the entries in the IIS Administrator for IBPMWeb, IBPMData and Messenger virtual Directories.

When all else fails…

o When all else fails, get another machine and install the web on it temporarily. Does it exhibit the same issues?

o Was the web installed via Terminal Services? If so, re-install from the console.

o Was the IPMWeb uninstalled and re-installed, or just updated over the older version?

o Was the web installed over a network share? If so, try installing from the CDROM.

If you are still unable to resolve the issue, get the following information:

1. What OS version and service pack does the webserver have installed?

2. Does the webserver also have other applications installed (besides IBPMWeb) and are they running under the same website?

3. What version of IBPMWeb are they installing/using and does that version match the backend IPM servers?

4. Is the customer using custom web applications? Were these recently implemented or altered?

5. Does the customer have Antivirus scanning the IBPMWeb and IBPMData folders? If so, have them exclude these directories for the real time scan.

6. What version of IE is installed on the clients?

7. What version of the J2RE is installed on the clients?

8. How many users are accessing the IBPMWeb at any given time?

9. How much RAM is installed, and how fast are the CPUs along with how machine CPUs are present.

10. Enable IBPMWeb logging. Login into the web with a user which has been granted the Web Administrator Policy; Click Administration; Choose Web Defaults; Check m_AcordeWebLogging; Save, and do an IISRESET. A log will be produced at the root of C drive called AcordeWeb<date>.log. After the error is reproduced and a log is created, turn web logging back off because logging is not thread safe. Supply this log to ImageSource tech support and it will be analyzed for it any info it can provide.

Leigh Woody
Program Manager
ImageSource, Inc.

Kofax moves to a pay-per-incident (PPI) system. What are your options?

As of August 3, 2009, worldwide technical support via telephone for all versions of Kofax’s VRS has been convert to a pay-per-incident (PPI) system.  Fujitsu offers a toll-free technical assistance support line for all Fujitsu scanners and software during the warranty period.  The scanner warranty includes phone support for Kofax VRS products provided with the purchase of Fujitsu Scanners.  Contact ImageSource for Fujitsu Scanners with VRS and post sales support.

Leigh Woody

Program Manager

Benefits of Remote Services for ECM Support

Would you land a plane in dense fog without radar?   Probably not, so why can it be difficult to get support representatives of  major software manufactures to dial in and assess critical business ECM servers to aid with troubleshooting?  I recently worked with a large ECM company that told me “Before that occurs ( dialing in ) … the customer needs to have the understanding that all we would be doing is observing the issue and that no troubleshooting or resolution recommendations would occur”.

What kind of a response it that!  I literally thought it was a joke.  I brought this to the attention of the technician’s manager and he agreed with his staff and said to me that in some occasions a remote session is the very first request (and occasionally only info) in new service requests.  He went on to tell me that occasionally something like – “my system isn’t working start a web session so I can show you”.   is frustrating for them because it is easy to get trapped into a complete unknown situation with no measurable exit strategy.  This can turn a quick 30 minute dial up session into an all day ordeal burning multiple resources at the expense of their other customer’s Service Request”.  So, they don’t want to help you because it may take up too much time?

Dumbfounded I went back to the support technician for more clues to this odd adaptation of quality customer support:

“To answer your question, it is not a joke. Since we do not know the cause of the issue we cannot state what the customer should do regarding resolution or troubleshooting. Therefore remote access is not going to accomplish anything outside of observing the customer system and possibly gathering new information. We often experience remote access sessions where the customer had the false expectation that just because we have remotely accessed the system we have an intimate knowledge of exactly what is causing the issue when in fact we are simply trying to discern the nature of the issue. The customer is then quite upset that we did not fix the reported issue. To avoid disappointment for the customer I felt it was of value to set an expectation of what the remote session would accomplish.”

This is a very experienced and knowledgeable technician who has already confirmed the validity of the issue and should be helping us figure out the solution to very complex problems by using all the tools available.  As the manager of the ImageSource Support Department there was no way that I was going to have a conversation with the client to tell them that I had a specialist on the line who has no intention of troubleshooting or coming up with possible resolution recommendations.

At ImageSource, It is our philosophy that we dial into a system because we don’t have an intimate knowledge of what’s causing the issue. If you had “intimate knowledge of exactly what is causing the issue” you would have no practical need to take a look.   We at ImageSource understand the value of getting in and taking a firsthand look to confirm the actual facts and maintain momentum to solve problems.  We believe that it is impossible to get the level of good data required to close service request and garner the benefits of informative research without truly understanding the environment. You know the adage… I picture is worth a thousand words.

Leigh Woody
Program Manager