Initially released to IWS Test on 20160127
Enhancements
Ability to Add Native Code before the </ EagleML> in XSLT
Previously, it was not possible to add native code before the </EagleML> and after </xsl:for-each> in XSLT. A new menu item ("As is the last element of EagleML") has been added to the context menu in XSLT grid to allow you to now add native code before the </EagleML>.
This issue was tracked as Item #137920.
Software Fixes
SplitString Does Not Support TAGNAMEPREFIX
The SplitString object did not support the TAGNAMEPREFIX parameter. New parameter has now been added to the object's input grid.
This issue was tracked as Item #137786.
EditCheck Expression Issue
Occasionally, EditCheck expressions are replaced by its other fields. This can result in data loss and incorrect rule execution. The issue occurs when the solution was saved with the no 'Expression' EditCheck parameter selected. The code was updated to resolve this issue. EditCheck objects are now correctly saved and loaded.
This issue was tracked as Item #137840.
Missing Template Attribute for XSLT Tasks in MC Cascading Solutions
An invalid preprocessing rule with no Template attribute is generated when using XSLT translator. This problem occurs when the 'MC cascading' export type is selected and XSLT Translator is not the first or last workflow step. To resolve this issue this missing attribute was added, targeting the previous step's stream outgoing folder.
This issue was tracked as Item #137959.
0 Comments