Directory Update v1.2

In the past two months, we have received a lot of feedback (and fortunately no bugs) on what customers would like to see in future versions of Directory Update. We had a v1.1 in development, but have gone ahead with additional features.   So, what can you expect?

• Ability to hide specific fields so they do not show up on the interface at all

• Ability to switch drop-down list boxes to text boxes (except country attribute)

• Ability to switch text boxes to drop-down list boxes

• Any drop-down list can include validated options that you provide

• Ability to hide an entire section, such as the phone number section or the address section

• Employee Type and Employee ID fields now included in the form, but hidden by default

• Custom Attributes (extension attributes) 1 through 10 available in a new section, but hidden by default

• Fields will do a reasonably good job of rearranging themselves within a section box if other fields are disabled.

• 10 day evaluation period instead of 5 days

The code is currently being tested, documented, and should be ready by 30 September, 2006.

All current customers are eligible for the upgrade; keep an on the site for the link.  Current customers will be notified via e-mail when the update can be downloaded.  If you have contracted with us for customizations, the customizations may be included in this version.  Look at the features list to determine if you want to upgrade back to the commercial version.

Prior to upgrading, please document all changes in your APPSETTINGS.XML file (such as the validated department, city, office, etc... lists).  The old APPSETTINGS.XML file is NOT compatible with the new version and you will need to recreate your customizations from scratch.  There are too many new options in the new version (such as the hidden tags) for the file to be compatible.

Many of the tag settings have been changed to make customizing the file more consistent and understandable, so please review the documentation on customizing this version.  For example, we removed a couple of places were you had to deal with "double negatives" in order to enable something.  For those of you that have used Windows Group Policy Objects, you can appreciate improving the readability of options by removing double negative options (i.e. "Enabling a feature" by disabling the GPO object.)