Released on Wednesday, June 24, 2009 - 00:00 +0100

SWiFT 7 Build 535 – Preview

June 2009

This release updates SWiFT from the Microsoft .Net Framework Version 1.1 to the Microsoft .Net Framework Version 3.5* Service Release 1.  With this change, we have taken advantage of many of the improvements in the .Net framework to improve SWiFT internally.  This has meant that SWiFT has had to undergo testing of all features and highlighted several issues that had not been reported but were present in previous versions.

This represents a significant move forward and will allow us to move the product forward in future versions.

This preview release has been heavily tested, but it is provided for you to test your procedures against and for us to resolve any issues before our final release.  There being no significant issues found, a final release will follow soon afterwards.  We strongly recommend that you do not deply this version to a live system unless you are completely confident that it is working correctly in your environment.

Metastorm eWork 6.x Users:

With the release of SWiFT build 534, our support for Metastorm eWork 6.x  entered extended support.  As a courtesy we have included the final release version of build 534 of SWiFT.ework6 in the SWiFT build 535 installer.  Any patches that may have been issued individually will not have been included.  This will not be developed further and will remain a .Net 1.1 web service.

Improvements

When Attachments are being stored to disk, if the file is not present on the disk, but is in the Metastorm database, the version from the database will be used. [SWF-227]

Power Tools users can elect to have alert lists obtained directly from the Metastorm database.  This has a particularly marked performance improvement for custom alert lists and filter numbering, particularly for large alert lists and for maps that hava a large number of folders (at any stage and for any user).  This was piloted as a patch to build 534, but is now configured through the SWiFT Management console.

Bug Fixes

·         An error in the Exposer administrator console resulted in incorrect display of the application event log page, making it difficult to use effectively [SWF-209][SWF-210]

·         The query criteria used to filter alert lists was using 'LIKE' even when it was not appropriate to do so [SWF-202]

·         There was a problem using Novell NDS SSO. [SWF-203]

·         It was not possible to submit or cancel a form, after the Metastorm client function eworkSetSubmitCaption had been called. [SWF-211]

·         The client side script functions eworkGetCurrentCol  and eworkGetCurrentRow returned -1 instead of the correct value. [SWF-228]

·         There were a number of issues relating to a row once it had been added to an editable grid [SWF-229][SWF-233][SWF-234]

·         A new client extension (SWiFT_ExtraCSS) that takes a string of CSS directives as its parameter can be applied to a form.  These directives will be added to the SWiFT form to allow a style to be modified on a per form basis.

* Please Note:  The .Net Framework versions 3.0 and 3.5 are extensions to the .Net Framework 2 and execute in the Common Language Runtime Version 2.x.  The version displayed in our software is the version of the Common Language Runtime to maintain consistency with IIS and other products.

Unavoidable Changes to Skins

When enhancing SWiFT, it is our policy to avoid making changes that affect third-party code such as custom skins and client-side scripting.  On this occasion, however, an issue that was significantly affecting users in certain circumstances has required an unavoidable breaking change.

In order to resolve a concurrency issue, a change has been made to a function used in various ASPX files, consequently a change will need to be made to most customized skins.

The line:

<%=GetResourceString("FOLDER_ACTION_START_CONFIRM",SWIFT_Skin.LanguageCode)%>

Must be replaced, wherever it occurs, with:

<%=FolderActionstartConfirmationMessage%>

Adding an Item to the Main Menu

On occasions, it is desirable to add a ‘button’ or link to the SWiFT main menu.  We have added a new feature that allows any number of buttons to be added to the end of the menu.  These are defined in Config.XML by adding an element similar to the one below to the <skin> element:

  <mainmenu>

    <menuitem href="http://www.google.co.uk" target="_new"

alt="Open Gooogle in a new window">Google</menuitem>

  </mainmenu>

Translation is not currently enabled for this feature ad this will only function if the fourth (cssLayout) parameter is set as true in the call to DHTML_MainMenu.

The element genetated will have an id in the form "SWIFT_MainMenu_n" where n starts from 4 and increments for each menu item.  This can be used to style the menu item individually.

SWiFT Locale Precedence

SWiFT may pick its locale settings up from a number of placed.  This has been re-visited to ensure that all settings come from the same source. The order in which a setting will apply is as follows:

1.       Form Setting (Client Extension)

2.       Custom format from Config.XML

3.       Custom format specified in SWiFT Console

4.       From SWiFT Users Selected Locale (Language)

5.       From Language specified in Config.XML

6.       From Language specified in SWiFT Console

7.       From Locale of user account running ASP.Net Worker Process.