Category Archives for "Solutions"

How eForms in Courts are Pioneering End-to-End Paperless Processes

Case Management featured

Courts everywhere use specialized software to manage their core business functions, not unlike any standard business process in any organization. ImageSource has worked with many courts to promote their paperless initiatives and integrate with their case management systems (CMS), whether they have proprietary systems or they are using popular software like Tyler, JTI, Justice Systems, or Thomas Reuters.

The reasons to utilize electronic forms in the courtroom are obvious. Eforms can enable an end-to-end paperless process, eliminate inked signatures, manual approval stamping, scanning and filing. They can also require that complete and accurate data is submitted.
Some case management systems include electronic forms modules, but they have real limitations. Because they are commonly static PDF documents that lack many of the benefits listed above, progressive courts choose to integrate a more robust eForms software for several reasons:

  1. Flexiblity of form structure
  2. Extended capabilities
  3. Data from forms can be pushed to other systems or standardized forms
  4. Control over final product or image
  5. Ability to easily build out additional forms not found in CMS

With these advantages in mind, let’s take a look at a real-world application to show the difference specialized, robust eForms software can make.

In the case of some California Superior Courts, eForms are revolutionizing traditional processes. In the past, attorneys and their supporting staff would have to sift through inapplicable fields to fill a paper form. Some of the fields had to be hastily filled during a hearing and then handed to the judge for a signature. The paper would then be delivered to court clerks, who would review and time stamp the document, scan and manually enter pertinent data into the case management system. The document would then be uploaded to a repository or the CMS, sometimes requiring more keying of index fields.

Flexible Form Structure & Extended Capabilities Simplify Completion

When advanced electronic software is integrated with a CMS, an eForm can automatically pull information from that database to pre-fill pertinent fields, verifying data, saving time and ensuring accuracy. Responsive form technology automatically only shows applicable fields, revealing more of the form only when certain actions are taken, like checking a box. Additional functionality enables the process to be completely paperless to provide additional efficiencies to the process. They include:

  • Pop-up calendars
  • Customizable branding
  • Electronic signature
  • Date stamping
  • Progress bar
  • Attachments documents or images
  • Calculator
  • Responsive sections (certain actions expose more fields)

Properly Integrated eForms Software and Court Case Management Systems To Deliver a More Powerful Solution that Functions Like a Single System

This eForm functionality is not just impressive, but exponentially valuable when integrated with existing case management systems, like Tyler, JTI, Justice Systems, and Thomas Reuters. The good news is that integrating some products, like our ILINX eForms, doesn’t have to be difficult or complicated.

Using ILINX eForms as an example, let me outline an example of the synergistic relationship between the two platforms for both the push and pull of data. As mentioned above, the eForm is able to pull data from the CMS to pre-fill and validate data in the form fields.
Upon completion and of an electronic form during a hearing, the same workflow used for submittal and approval can begin a number of essential processes to push data. First, it can update the case management system with the data collected. Second, the data can be transformed into a digital document that looks like an official paper document that can be stored in the CMS, stored in a repository, shared or printed.

This image automatically retains relevant metadata so it can be easily searched for, making retrieval a breeze. Lastly, the data collected can be pushed to standardized forms, like the ones provided by the Judicial Council of California for Superior Courts to use, fully automating that process.

Data collected on eForm can be automatically pushed to a standardized PDF form, including signature

 

A Dedicated Form Software Allows Limitless Possibilities for Forms & New Efficiencies They Deliver

Imagine the possible applications across your organization for any process that needs to gather information and deliver it in a specifically structured document, or as raw data. Using the right form builder, your IT team can generate a wide variety of eForms internally, enabling granular control over function and the flow of information.

Using the courts as an example, a flexible eForms product like ILINX, can be extended to integrate with any number of business systems for better access and automation. Forms can be integrated with accounting systems for online invoice submission, status and resolution, procurement and expense reporting. Forms can be utilized by HR for onboarding, time-off requests and address/name changes. Public requests for court documents can be made through a web form. Payments for requested documents or fines can also be collected through a form. All this using one flexible platform.

These points highlight just how powerful the integration of a robust electronic forms platform can be, demonstrating the value that they add not just to a court system, but to virtually any organization.

For more information on ILINX eForms, visit our website, email us at info@imagesourceinc.com, or call (360)943-9273.
To learn more about ImageSource, and all of the content management services we provide, visit us here.

Migrating 85 million documents from Oracle 10g with no data loss—a process, not an anomaly

ImageSource has been successfully executing migrations, large and small, to and from content repositories since 1994. Recently, we completed a mammoth project for a global financial information services company in which we migrated 85 million documents from a deprecated Oracle 10g IPM system to ILINX Content Store in 9 months with 99.99995% accuracy. That’s zero loss of data, except a few hundred docs that were already corrupt in the source system!
The speed and accuracy of this project can be attributed to 3 important factors that made the content migration successful:

  1. We assembled a strong technical team.
    The team for this project consisted of an Oracle 10g technical subject matter expert, a seasoned PMP Project Manager with years of experience managing Oracle 10g migrations and a SQL database expert. This team provided all the expertise required to plan, execute and audit this size of migration.
  2. We used time-tested methodology from years of experience performing similar data migrations.
    Given the mission critical and high transaction volume nature of the legacy Oracle 10g system, maintaining business continuity was critical. A detailed Migration Plan was developed addressing all content to be migrated, associated requirements (e.g. retention of annotations, excluding content that had or would meet document retention\destruction requirements during the duration of the migration, etc.), and auditing requirements. A detailed audit and migration report was performed and delivered to provide an accounting for every single document in the source system.
  3. We utilized powerful, configurable technology.
    We leveraged multiple tools and techniques in the execution model (e.g. temporary migration environment that included replicated data, multiple instances of ILINX Export, etc.) to be able to complete the migration. By creating a temporary migration environment, we were able to leverage the power of ILINX Export, ILINX Import and a multi-instance model to perform the migration in record time. The numbers speak for themselves: 85M docs, 9 months, zero data loss.

We’ve used a similar services formula for migration execution large and small—your migration doesn’t have to be massive like the one mentioned above to give you great ROI. That, and the right software mix, will eliminate headaches from the equation the next time you have to migrate content.
If schedules or other factors outside your control don’t allow time for a full migration prior to going live with your new system, we have a feature in ILINX Content Store that will allow customers to turn off their normal end user access to your legacy system on day one of using the new system and still pull content from the legacy system through the ILINX interface, read more about that here. This enables significant benefits that include smarter resource allocation within your operating constraints and migration flexibility. Contact us for more information.

Gene Eckhart, PMP
Project Manager
ImageSource, Inc

Transferring ILINX Release Configurations When Upgrading

Starting with ILINX Capture v6, the Release configurations are stored within the ILINX database. In ILINX Capture v5x, the ILINX Release configurations were stored in XML files on a disk. ILINX Capture called ILINX Release using a SendAndReceivedReply IXM. The change to store the settings within the ILINX database is very useful for a number of reasons: Release settings are part of the batch profile allowing for simpler migrations between environments, Release is much easier to configure, all configurations are in the database, etc. However, this change can create some extra work when upgrading from ILINX Capture 5x to ILINX Capture 6x. Because of the different architecture, ILINX Release needs to be completely reconfigured for the existing batch profiles. In addition, the Release XML doesn’t change, but there is a shortcut that can be taken. After you have upgraded ILINX Capture to v6, you’ll notice a new IXM in the palette: ILINX Release IXM Icon

The existing ILINX workflow will likely have a SendAndReceiveReply IXM on the map that the 5x version of ILINX Capture used to call ILINX Release. Most likely, it would look like this:
SendAndReceiveReply_IXMTo configure ILINX Release for ILINX Capture 6x, the SendAndReceiveReply IXM will need to be removed from the map and a Release IXM must be dragged onto the workflow map in its place. Once the new Release IXM is on the map, it will need to be configured. This is where the shortcut can be taken. Instead of having to manually enter in the correct URLs, map the metadata values, and configure any other settings, do this:
Configure and save Release with some place holder settings: I normally leave the settings at default and enter in the bare minimum:

  • Job Name
  • User Name
  • Password
  • Batch Profile
  • Release Directory

Once ILINX Release configuration is saved and the workflow map is published, there will be a new entry in the ILINX Capture database Capture WorkflowAppSettings table. The CaptureWorkflowAppSettings.SettingsXML column is where the Release configuration is stored. Now it’s time to update the SettingsXML column with the XML from the ILINX Release 5x job settings file. The Release job should be on the ILINX Release 5.x server at c:ProgramDataImageSourceILINXReleaseSettingsJobs. The only caveat here is to be sure to place single quotes around the XML content. Here is what the SQL update statement would look like:

update [ILINX CAPTURE DATABASE].[dbo]. [CaptureWorkflowAppSettings] set SettingsXml = ‘COPY AND PASTE ALL TEXT FROM 5.4 OR PRIOR RELEASE JOB SETTINGS FILE HERE’
where settingsID = ‘APPROIATE ID HERE’

Following this procedure can save some time if upgrading an ILINX Capture 5x system that has a lot of batch profiles. A lot of the time spent on the upgrade could be in the ILINX Release configuration. If I was upgrading a system with only a few batch profiles, I would probably just reconfigure them. If I was upgrading a system with a lot of batch profiles, I would go through the above steps to save some time.

John Linehan
Sr. Systems Engineer
ImageSource, Inc.

Failover Cluster Troubleshooting

There’s nothing quite like logging in to a customer’s system first thing Monday morning only to be greeted with this:

Windows Powershell Cluster Report

I discovered this when I wasn’t able to log into the customer’s ILINX Capture implementation. The logged error (failure to locate the SQL Server) led me to take a look at the SQL Server’s configuration to confirm that its service was not running on either node of the cluster, and the error I got when trying to start that (a clustered resource could not be activated) led me to check on the clustered resources themselves.
Continue reading

Implementing SQL FILESTREAM Part II

Last month I wrote about enabling SQL FILESTREAM with ILINX Content Store. After discussing this with a few people, I think I should share some more information and reiterate a couple points.

For Existing Applications:
As I mentioned before, the decision to enable FILESTREAM should be done during the planning phase. If you perform this process on an application with a lot of content, it can be a very time costly endeavor with a big performance impact to the server. Also, after the move from BLOB to FILESTREAM, you could have a fragmented database. The BLOB to FILESTREAM process can definitely be done on an existing system, just be sure to plan accordingly and allow for sufficient time.

After step #10 of my previous blog post (all the data is copied and you have deleted the BLOB column), you will notice that the database file size hasn’t decreased. This is remedied easily enough be executing a DBCC CLEANTABLE command. The DBCC CLEANTABLE command will reclaim the space from the dropped variable length column. For example, if your database is named ILINX_CS and your application is named Sample Application, the query to do this is:

DBCC CLEANTABLE ('ILINX_CS','[dbo].[Sample Application]',10000)Continue reading

1 2 3 17