Directory Update v1.2 Release Notes

We are pleased to be releasing Directory Update v1.2 sooner than expected. However, like v1.1, this updated version is an interim release on the way to a final set of features that we had hoped to release in the v1.x timeframe.  The features in this release are also intended to support some specific feature improvements that have been requested by customers and potential customers.  

What Do I Need To Know Before Upgrading?

• The code has been updated to use the Microsoft .NET Framework v2.0. You must download this from Microsoft if it is no already installed on your web server. This is ONLY required on the web server on which Directory Update is installed.
• If you are running any version in the v1.0.x family, the APPSETTINGS.XML file from that version is not compatible with the new version. There were too many changes to the XML file for it to easily be converted or used with v1.2. If you are running v1.0.x and have made a significant investment in customizing the drop-down lists. You can cut and paste any of the <value> ValueName  </value> tags in to the new XML file.
• Firefox is not supported in v1.1 or v1.2.  Firefox actually works, but it is not pretty.  In changing the interface to allow fields to be hidden from view, the tags that are used to re-arrange the fields and remove any "blank spots" does not work with Firefox, only Internet Explorer.  We have been researching the problem and found other web developers with the same issue.  We hope to fix this in a later release, but it may require a complete re-write of the interface.
•  Previously, we had planned to include the Manager field in this release, but that requires more coding and testing so we decided to release v1.2 without the Manager field. v1.3 will include the Manager field.

What's New?

The primary reason this version has been released was to adopt some specific customizations and changes that have been requested. Here are the new features and functions. 

• Custom Attributes 1 through 10 can be shown on the User Information form
• Custom Attributes are hidden by default
• Employee ID, Employee Number, and Employee Type fields can be shown on the User Information form
• Employee ID, Employee Number, and Employee Type are hidden by default
• First name, Last name, Middle Initial, and Display Name can be edited by the user. This is disabled by default and we recommend enabling this ONLY if you are positive you want to let your users manage this information. This was included specifically for one customer's request, but we included it in the main code base.
• The setup process includes an extra step. This is in the documentation, but we wanted to make sure it was seen. In IIS Admin, highlight the Directory Update virtual directory that was created during installation. Locate the ASP.NET property page and confirm that the ASP.NET Version is v2.0.xxxx rather than v1.1.xxxx.

What's Fixed?

• By moving to the .NET Framework 2.0, a rare problem with the WebUIValidation.js script was fixed. This was a problem with the .NET Framework, but we saw this once in production. .NET Framework 2.0 also includes some new development capabilities that will allow the interface to be more efficient.