Upgrade Guide to Websydian Version 2.5

• Websydian Moved to AllFusion Plex Version 4.0
• Header File Changed
• Hidden displayed as-Field Ignored
• Inheritance Paths Changed

This upgrade guide is aimed at development sites that have already build AllFusion Plex models based on Websydian 2.1 and want to move those to Websydian version 2.5.  If the AllFusion Plex model is based on a Websydian version prior to 2.1, the upgrade guides for these versions should be read and the guidelines in all the upgrade guides applied.

A number of changes have been made to the internal structure of Websydian, but these changes should not affect existing Websydian applications unless they have been using any of the internal parts of Websydian.

Websydian Moved to AllFusion Plex Version 4.0

In version 2.5 of Websydian, the Websydian pattern libraries has been moved to AllFusion Plex version 4.0.  In order to work with Websydian version 2.5, all development group models must be moved to AllFusion Plex 4.0.

Header File Changed

The Websyd.h header file has been changed and the code in the old header file has been moved into a lib file (websyd.lib).   This means that the old header file must be replaced by the new and in future projects, the Websyd.lib lib file must be included in the Generate and Build Options panel.

Hidden displayed as-Field Ignored

When a field with a displayed as-triple definition is in the Hidden variable of an Event Handler function, the field will not be generated as a hidden input field in the HTML Form for that Event Handler function.  Normally, it does not make sense to have such a field as a hidden input field because the value of this field will be set to the value of the scoped displayed as-field when the Event Handler function processes the request.

Inheritance Paths Changed

The inheritance path has been changed for the Event Handler and the Page Generator functions.  This may only infect the design, if any references have been made directly to any of the changed or deleted low-level patterns (which is not very likely).

Exactly what patterns have been changed can be seen in the Changes in Inheritance Paths section of the Version 2.5 What Is New document.