IWS Release Notes - Version 1.0.1.387

Owned by Former user (Deleted)
Last updated: Sept 04, 2024 by Kinga Huszno
2 min read

Initially released to IWS Test on 20150422

Advanced Notification

Microsoft .NET Framework to be Upgraded
A notification has been added when you initially log into IWS to alert you to the upcoming .NET 4.5 upgrade. Please note that IWS will be upgraded to use Microsoft .NET Framework 4.5 in the near future. IWS currently uses .NET4.0. This change is being made to align with Eagle's core software, in 2015R2 the New UI upgraded to 4.5. If you do not currently have .NET4.5, you will need to download it once the change is made in order to access IWS. Microsoft .NET4.5 is backward compatible and will also work with the current version of IWS. We will also be introducing a new shortened .exe name for IWS to resolve some isolated issues with the filename length. When these changes are implemented, you will need to perform a one-time action of uninstalling and reinstalling IWS. More details will be provided at that time. Testing is currently underway. These changes are expected to be implemented in the next several weeks. If you have IWS users that still have Windows XP running on their desktop, please note Microsoft .NET Framework 4.5 is not compatible with Windows XP. 
This issue was tracked as Item #129522.

Enhancements

Support for New EagleML Types

IWS was enhanced with support for the following new EagleML types:

  • WarehouseBrokerTradeQuote

  • GeneralLedgerActivity

  • AccountingCash

  • AccountingAssetCash

  • AccountingReclaimCash

  • TradedCashActivity

These new objects can be found in types list for EagleML format in the Task Format forms.

This issue was tracked as Item #129658.

Software Fixes

Default Proxy Setting Support Added

Default proxy settings support was added to IWS. IWS now reads proxy settings from IE or system and uses the settings for network connections. This change was made to address a specific IWS login issue experienced by a client.
This issue was tracked as Item #129448.

 

Export Issue for AddIfNotNullToAll and ExcludeElementsWithValues XSLT Parameters

If you used variables in the expressions of the XSLT Translator and AddIfNotNullToAll or ExcludeElementsWithValues parameters, the variables may be not wrapped into 'xsl:if' elements upon export. The code was updated to resolve this issue. The variables are now properly exported.
This issue was tracked as Item #129413.

 

Issue with Progress Bar in Solution Explorer

If you closed a solution in the process of refreshing it in Solution Explorer and then re-opened the solution, the green progress bar in the Solution Explorer remained in an in progress state. The code was updated so that the progress bar will reflect appropriately.
This issue was tracked as Item #129459.

 

Updates to Generic Extract Object

The list of available extracts and filters in the Generic Extract objects properties and Extract format forms was updated to include the current state of latest EagleML package. In addition, you are now allowed to add custom filters to the Additional Filters grid by adding rows with Parameter and Value columns populated.

This issue was tracked as Item #129486.


Unnecessary Errors When Opening Rules When Data File Not Available

When you open rules using Solution Explorer in File System mode, you can get multiple error messages if the attached data file is not actually present on the server. These errors have now been suppressed, since this does not affect the rule execution.

This issue was tracked as Item #129412.