Initially released to IWS Test on 20150415
Advanced Notification
Microsoft .NET Framework to be Upgraded
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.
This issue was tracked as Item #129451.
Enhancements
Introduced New ExcludeElementsWithValue XSLT Parameter
XSLT translators were enhanced with a new ExcludeElementsWithValue parameter. This feature can be used by adding the XSLT General Params object and setting comma separated values for this parameter. Nodes with these values will be excluded from the result XML output.
This issue was tracked as Item #128761.
New Feature to Run Simple Template Solutions
IWS was enhanced with a new feature to allow you to run simple template solutions. You can now run transform and load solutions using Run button on Solution toolbar. After clicking on Run from the toolbar, the solution will be published and a Run MC Process window will be shown. You would then select a data file to pass into the process. For transform and load solution you are able to run only transform task. To do this, check Run Transform Only checkbox. Next, click Run and the file will be sent to MC Process.Note:
Info |
---|
|
...
|
This issue was tracked as Item #128761.
Software Fixes
Removed Invalid Source Format Options
Previously, EagleML-2-0 and EagleDBML showed as format options on the Source side, but they were not actually valid choices. If you selected either, all format options on the Destination side would be grayed out. This caused some confusion, so the EagleML-2-0 and EagleDBML have been removed from the Source format options altogether. The XML source format should be used instead for these source types.
This issue was tracked as Item #128716.
...