IWS Release Notes - Version 1.0.1.444

Initially released to IWS Test on 20150909

Enhancements

New Automatic Mapping Option Available for DB Request Object
A new Automatic Mapping option was added to the DB Request Message Exchange object. With the feature enabled, the request can be correctly executed if the output parameters are not defined. The Automatic Mapping option can be found in the Object Settings popup window of the DB Request object.
This issue was tracked as Item #133613.


Introduced New cmDeliveryStream Property to ExecuteCM Object
In the ExecuteCM object, the new WRF parameter of cmDeliveryStream has been added. You can enter the name of the delivery stream here.
This issue was tracked as Item #133607


Enhanced Content Created by Download Publishing Package
When you export by using the Download Publishing Package option off the main IWS menu, IWS creates an the overall package that now includes all references to the packages and source. This main package can then be imported manually to the Message Center Editor.
This issue was tracked as Item #133508.


Solutions Can Now Be Compiled From Solution Cache on Client
With the Download Publishing Package function, you are now able to build the package directly from IWS using the Export Dialog form. This feature is available only where the Solution Cache are downloaded and valid. Otherwise, the original Download Publishing Package functionality will be the only option.
This issue was tracked as Item #132522.

Software Fixes

Multiple Listings in DB Tables Tab
In the DB Tables tab associated with XPanel extensions, the DB schemas were displayed multiple times. A new 'Load Tree of DB items" button has been added to the DB Tables tab. When you click this button, the db items be loaded and displayed properly.
This issue was tracked as Item #129841.


MSSQL Only - Issue Displaying Tags in Existing Tab
When you added a new tag for solution, it was not displayed in the Existing tab. This issue affected MSSQL environments only. The code was updated and tags are now properly displayed.
This issue was tracked as Item #133487.