Attention: We are pleased to announce the new iMIS Developer Resources website. Thh new site has replaced this legacy iMIS Community and includes standards and guidelines, best practices, and how to articles on developing iMIS applications. You will also find a new Developer Community where you can add blogs or contribute to discussions. If you are an active client or partner, you already have access to the site. If you cannot access the new site, please submit a ticket to Technical Support. The site can be accessed from the Client Global Support Portal (Support > Resources > iMIS Developer Resources).

Given our transition to the new iMIS Developer Resources site, this legacy iMIS Community site has been officially deprecated to a read-only archive as of December 31, 2016. After a one year sunset period (effective December 31, 2017), all page requests to the original archive will redirect to the new site. If you have any suggestions or articles you’d like for us to post, please contact

The Fallacy of Premature Optimization

I came accross this article, which goes into one of the major software design misconceptions out there. I've heard this echoed many times: XML doesn't have to be compact, the network will get faster; Java doesn't have to be fast computers will get faster, etc.

I've also seen many systems bogged down with fundamental designs enforcing poor performance. Most of the time the problem is designers that don't understand the impact of shared resources on a web server. They worry about CPU cycles on individual requests when they use a property heavy remote object, or abuse a database with multiple small requests in a transaction.

iMIS Things To Do On A Rainy Day

Attention: iMIS System Administrators, iMIS Technical Staff and iMIS Consultants

Have a spare hour or two, or is it raining outside so you have some time to spend on iMIS instead?

There are many things you can do to tune iMIS with an hour, or just a few hours, of time.

But what exactly would you do?

These book pages are designed to give you some ideas, and each one is planned to include a checklist of the specific action steps you should take to complete the steps.

Program summary: High-tech training for low-tech people

ASTD Austin July 21, 2006

Program: High-Tech Training for Low-Tech People
Presenter: Katrina Schold, Manager of Client Education & Support at Convio (previously at Dell, Tivoli/IBM,, and Best Software)

Topic: How to adjust training to transfer appropriate technological information to a non-technical audience: tips for reading and managing a diverse audience, responding to signals, and explaining technology despite a student's inexperience or misgivings.

what iMIS tells you about the Word Merge install

There are several bits that need to be set up to enable using Word Merge inside iMIS -- the Word .OCX needs to be installed, MS Word needs to be installed on the workstation, and the Word shared document folder needs to be set up and valid (File/System Setup/Choose MS Word Folder). The Help/About/System Info window provides information about the state of these items. This window lists versions for all the ActiveX components in iMIS, and the AsiWordInt.ocx version is at the end of the list. The table below shows possible values for the AsiWordInt.ocx version and what they mean.

complete validation of email addresses

An email address like follows the syntax rules for an address. Simple string checking can confirm that the address includes an @ sign, a period, and no spaces, but it doesn't confirm that it's an address where email can actually be received. iMIS currently does simple string checking on email addresses; I'm posting this to keep track of some additional information, in case there's a request for an email validation feature/module someday. Here are a couple of component vendors that do full-up checking (syntax rules, DNS, and SMTP). The first link has a lot of information, including examples of strange-but-valid email addresses. Note that embedded spaces are technically correct, but in research for the Medina release, we found that some email providers don't accept addresses containing them, and so iMIS doesn't allow embedded spaces for Medina -- disallowing embedded spaces in email addresses was a requirement for Medina. Here's the original ARPANet email standard from 1982: