Looking for an Oracle IPM replacement?

You have hundreds of thousands, maybe tens of millions, of documents in your old Oracle IPM 10g system with only 6 months before Oracle closes the support door on that product forever. Or maybe you’re running an Optika Acorde or Stellent IBPM system which has been out of support for years. You’ve looked at the new Oracle 11g platform and it’s too heavy, complex, and missing many key capabilities that you need, features like: external searching with Linked Servers, COLD support, Office and .NET integration points, easy setup and maintenance, and a workflow system that is actually usable for someone without a PhD. Oracle is clearly, and publically, going in a different direction and moving away from traditional enterprise imaging and transactional content management.

And even if you knew of an appropriate replacement technology, how are you going to migrate all of that content out of IPM without disrupting your business? What product vendor is going to know enough about your old IPM system to be able to get the content , applications, saved searches, workflows and profiles moved to their platform? Oh, and you don’t want simply to replacement on product for another – you want a good return on this migration investment!

ImageSource has been delivering and servicing Optika Acorde, Stellent IBPM, and Oracle IPM systems for nearly 20 years (don’t get me started on eMedia!). We recognized Oracle’s change in direction several years ago and have created the perfect replacement solution for the retiring 10g product. The ILINX suite offers the same content management capabilities as IPM but goes way beyond that. In fact, ILINX is more powerful, easier to deploy, use, and maintain, with better scalability, 100% browser-based, built-in retention management, more secure, free mobile clients, cloud-ready, built on the latest Microsoft technologies.. I could go on and on.

Check it out for yourself at www.ilinx.com

Join the dozens of other Oracle IPM customers that have made the easy switch to a better, more powerful ILINX solution!

Randy Weakly
VP of Software Development
ImageSource, Inc.

Moving To The Cloud

For some interesting reading, range about the Internet for articles detailing the way the software world has changed in the past few years with the success of companies like Facebook and similarly ubiquitous, social-node technologies. Those companies have fostered the advent of the DevOps strategy, which is more a paradigm shift in corporate culture than merely a mechanical development/quality assurance/deployment strategy, and it demonstrates a new way of thinking about deployment scaling using the cloud (with an unbelievable number of servers available) while maintaining an aggressive development schedule. Sprint-cycle application development and cloud-based deployment are the order of the day for these newer entities. No longer does dev sit in a development cycle of a year or more, but rather a cycle that is measured in months at most, or weeks – even days. Getting customer-requested features quickly into the product and out to the customers is still job one, but – Oh, hey! – the difference in implementation! Ben Horowitz Article “How Software Testing Has Changed”
Continue reading

Is it a batch, a document, a page or a file?

“The ability to save compound documents blurs the definition of “pages”, which is sometimes confusing for knowledge workers.”

The ILINX product suite, as well as most content management systems, saves content in batches. A batch can contain one or more documents and a document can contain one or more pages.

“This made complete sense when we we’re all saving only TIFF images.”

ILINX has the ability to store diverse file types in a single compound document. This includes standard image file formats along with virtually any type of electronic document, such as Microsoft ® Word, Excel, PowerPoint, Text, Video, audio, web content, etc. What used to be pages in a document may now include, as an example, a single page TIFF, a Word document with 35 pages, and a PowerPoint document with 12 pages, all combined into and saved as a single compound document that displays as three pages when indexing.

“We just might have to think about revising our terminology to keep up with all the advances in content management.”

Robert Hughet
Quality Assurance Mgr.
ImageSource, Inc.

How to run SQL code against an Oracle databse

Context: ILINX Capture, ILINX Release and Oracle IPM 11g

Problem: A customer wanted the ability to run some custom SQL code against an Oracle database after a doc has been released to Oracle IPM 11g.

Solution: Place the built-in DatabaseLookup IXM after Release and use the return value from Release to call Oracle. Below is a screen shot of the workflow:

phong

Phong Hoang
Development Manager
ImageSource, Inc.

ILINX Capture Mobile for iOS and Android Update

ILINX Capture Mobile extends document capture, normally limited to scanners inside of your organization, out to mobile devices in the field.

  • Capture documents on your mobile device via its camera or existing photos folder
  • View and select batch profiles and associated document types live from your internal ILINX Capture system
  • Index and send documents directly into your ILINX Capture workflow for processing, all from your supported mobile device

ILINX Capture Mobile is great for city/county inspectors, accident photos, realtors, appraisers, or anyone needing to document information remotely or even just expedite travel expenses.

Look for the full details coming soon at: http://imagesourceinc.com/

Robert Hughet
Product Manager
ImageSource, Inc. 

Defining Batch Profiles in ILINX Capture

In ILINX Capture, the most basic unit is a batch profile. A batch profile is a container that includes batch fields, one or more document types and a workflow. It is unique, self-contained and completely independent from each other. In general, you would want to create a batch profile for each unique workflow process in the system.

If you have multiple doc types that mostly follow the same process, you should think about creating a single batch profile to hold all the doc types. With this setup, you can then use permissions to give users access to their specific doc types. Furthermore, within the workflow designer you want to break your workflow logic into common processes, shared by all doc types and specific doc type sub-flows. If you find that you need to create too many sub-flows, re-evaluate the relationship between a batch and doc types and see if you can fix the problem.

The goal is to create unique workflow processes so that system maintenance is easy; and one way to deal with that is to avoid duplicating batch profiles that are performing the same tasks.

Phong Hoang
Development Manager
ImageSource, Inc.