Initially released to IWS Test on 20150204
Enhancements
Show Existing Solutions in List View
Previously, when you selected Open Solutions or clicked on Existing under New Solutions, each solution name would be displayed along with an icon. These icons used by a considerable amount of real estate and currently added no additional value. Therefore, the existing solutions will now show in a simple list without the icons by default. You can still switch to display the icons if you prefer by clicking on the view buttons in the content section of the window. The icons will be enhanced in a future release to be more meaningful, which is why the option remains to switch to this other view.
This issue was tracked as Item #125094.
...
IWS was enhanced to include XSLT task extensions. With XSLT task extensions, you have the ability to map recently added fields in a separate solution. This approach is easier than doing in an existing solution, where you would have to refresh the source and destination and restore all existing mapping. To leverage this enhancement, you would already have your existing XSLT transform solution. Then in IWS, choose Templates and the Simple XSLT Translator Extension template. Next, select the desired XSLT transform solution and the available XSLT Translator to extend. Your solution will be created. Populate the source and destination grids with the extra fields and map necessary elements. Save your solution and publish. The extension transformation will now be attached to base XSLT transform task. You can then use the base XSLT transform process to transform common incoming files and incoming files with the extra fields you mapped in extension solution.
This issue was tracked as Item #126743.
...
A ResultFileName Pattern Parameter for Tasks has been added. This addition allows for the ability to set additional characters to the output filename for XSLT tasks in workflow. As an example, here is a filename that uses a ResultFileName pattern of:
| Panel |
|---|
MYDATA: 20150202-074847-1IQZE9CZCBN301CC5_MYDATA_xslt_wrf__xml~_16YWI6A14DN5JRMEDATA~.dat |
This issue was tracked as Item #126949.
Software Fixes
Display Issues With Expand/Collapse
It was possible to encounter some display issues in the Translator worksheet if you performed multiple clicks on the expand button for a populated Source or Destination objects. The code was updated to resolve these issues.
This issue was tracked as Item #125916.
...
PACE Event is now automatically created when you export a schedule workflow from IWS at the first time. The created process will have the same name as your workflow.
| Info |
|---|
...
The latest EagleML package is required to leverage this change. |
This issue was tracked as Item #126707.
...
Previously, IWS did not create streams for XSLT tasks. The code was updated so that IWS now automatically creates the Message Center Stream for the execute transformation.
| Info |
|---|
...
It is important that XSLT transformation which will called by the object be in the current solution. |
This issue was tracked as Item #126842.
...
The Simple XSLT Translator Extension template has been renamed to XSLT Translator Extension Template. Also, the word extension also contained a misspelling which was fixed.
This issue was tracked as Item #126908.
...
If you added your task to the Task Lib, its subtype would be always reset to Task Loader. This was true for all tasks except XSLT ones, which did save the subtype correctly. The code was updated to resolve this issue. These library items are now correctly saved and loaded appropriate as Task Translator, Task Loader, Task Extractor or Adapter.
This issue was tracked as Item #126938.