Update Announcements

[RussCraig]

In reading some posts, I've seen it mentioned a few times about an update to Profound UI, namely an update for 05/06/2010. Would we be notified of this updated version?

Also, how would we go about updating? Would we just install the updated version over the existing version? If so, would this affect any changes we may have made to the Profound UI login screens?

Thanks,
-RC

[Rob]

Yes the update was loaded onto our web site last night. I will be attempting to contact those people who were waiting for an update.

To install the update, just run the install process as you did originally. If you chose to customize the install settings originally you will need to select the same settings to update.

If you have made any custom changes to your HTTP configuration since the original installation, you can un-check this component. In most cases this will not be necessary.

The PUISAMPLES library is replaced so make sure this library is not locked (eg in your client access session library list).

You have raised a good issue regarding the customized Login/Error/EndSession screen. This is DDS source member PUISCREENS in the PROFOUNDUI library. We may be replacing this at the moment so if you have customized any of these screens (including the login screen), I recommend you make a copy of the source member before installing the update. We will need to make a change to the installer if this has been an oversight.

[RussCraig]

Yes, when installing a new version (this occurred with 2.0.2 and 2.0.3), the PROFOUNDUI/PUISCREENS member does get replaced. So if a user has customized these screens, they must save a backup in a different library, install the new version of PUI, then copy the screens back into the PROFOUNDUI library.

Perhaps add a checkbox option in the "Advanced" section of the install process that would allow a user to choose whether or not to install the default screens.

Also, do you have any form of "Release Notes" that detail changes in each version?

Thanks,
-RC

[Rob]

Yes you are correct. Two tasks on our To Do list include checking for the existence of the SCREENS display file to avoid overwriting it, and providing version history / release notes for each update. We do hope to have these completed ASAP