IWS Release Notes - Version 1.0.1.351

Initially released to IWS Test on 20150211

Enhancements

IWS Now Officially Supports Ping

You can now use IWS in Eagle environments using Ping authorization. When using IWS in an environment using Ping authorization, in the IWS Log in screen, type your network user id into the User Name field and your network password into the Password field.
This issue was tracked as Item #119357.

Software Fixes

Issue Using an Ampersand in Mapping

If you used an ampersand symbol ("&") in your mapping, you would get an unexpected token error. As a workaround, you had to actually change the "&" to "&" in your mapping. The code was updated so that IWS can properly handle an ampersand symbol in your mapping now.
This issue was tracked as Item #124546.

Issue With Transform and Generic Load Template When Using XSLT

If you created a XSLT transformation using the 'Transform and Generic Load' template, you would get an incorrect workflow structure with MC Translator for the transformation step. The main workflow would incorrectly show the object as a regular Translator object instead of the XSLT Translator object. The code was updated to resolve this issue. XSLT Translator object will now show on the main workflow for XSLT transformations.
This issue was tracked as Item #127015.

MAP Files Not Included in Export Package

When you clicked on the Publish button, MAP files were not included not in the export package. The code was updated to resolve this issue and MAP files will now always be included when you publish.
This issue was tracked as Item #125142.

Export Issue When No Task Format Set

If you tried to export a task with no task format set in the Task Source object, you would get an invalid message format on export. The code was updated to avoid this issue. When creating new MC task, IWS will now force you to set the format.
This issue was tracked as Item #125545.

Invalid 'Encrypted' Parameter Generation for FTP Message Exchange

If you enabled the 'Encrypted' parameter in 'Read data from FTP' or 'Send data to FTP' Message Exchanges settings, the parameter value was exported incorrectly. The code was updated to resolve this issue.
This issue was tracked as Item #126437.

Invalid OLEDB SQL Request

If you tried to create 'DB Request (SQL)' Message Exchange or Destination DB Request using OLEDB driver, you would get an invalid request on export due to a space in the driver name. The code was updated to resolve this issue. The space was removed from the 'DRIVER' attribute value. In addition, all occurrences of 'OLE DB' have been changed in the user interface to avoid any confusion.
This issue was tracked as Item #126942.

Issue with Duplicate Custom Parameters

There was an issue if you used custom parameters of the same name. EJM can receive parameters with the same name, but will only process the last parameter. Similar logic has been added to IWS, so that it will now ignore any doubles and save only one parameter.
This issue was tracked as Item #126943.

Issue Closing Rules

When you closed a tab with MC rule or include file, you could occasionally get an error message about failed file download. The code was updated to resolve this issue. The incorrect file download attempt was removed and this error will no longer be raised.
This issue was tracked as Item #125892.

Issue Error Handling Caused IWS to Close

There were still a few instances were IWS could close unexpectedly when encountering an error instead of displaying an error message. The code was updated to add proper error handling in these cases and display the error.
This issue was tracked as Item #123173.

Issue when Intranet Involved

IWS did not properly handle if Ping or Eagle used an intranet site. The code was updated to resolve this issue. You can now log into IWS if an intranet site is involved.
This issue was tracked as Item #127193.

Incorrect WRF InboundDataFile Mask

In some cases, IWS generated the WRF file incorrectly by having the inboundDataFile mask as:

instead of the correct format of:

The code was updated to resolve this issue.
This issue was tracked as Item #127205.