Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Initially released to IWS Test on 20140924

Enhancements

Added New Filter Tabs to Source and Destination Objects
New Filter tabs of "All" and "Mapped" have been added to the Source and Destination Objects. These tabs are available only for the XML destination type. You can use the "All" tab to hide header nodes, as usually these nodes are usually not necessary to map. The "Mapped only" tab shows only the mapped nodes.
This issue was tracked as Item #123110.


ForEach Inherits Properties from Main Worksheet
IWS was enhanced so that the ForEach object will now inherit its properties from the main worksheet.
This issue was tracked as Item #123115.


New XSLT Call Template Feature Within ForEach
 A new XSLT Call Template feature is now available within the ForEach object. The XSLT Call Template can generate the following XSLT code:

<xsl:for-each select="//referenceTransactionMessage:referenceTransaction">
<xsl:call-template name="cs_t_referenceTransaction_template" /></xsl:for-each>

This issue was tracked as Item #123116.

Software Fixes

Switched Order of Checking for The Existence of IWS Streams
Previously in IWS when you logged into an environment, it initially determined if IWS streams existed in Message Center by first checking for the existence of "eis_" stream names and then checking for "iws_" stream names. The "eis_" streams were from a very old, initial version of IWS and most clients have only "iws_" streams in their environments. Therefore, the order was updated to check for the existence of "iws_" streams first. If an environment has neither the "iws_" or "eis_" streams, you will receive an error message indicating this issue.
This issue was tracked as Item #123108.


Issue Adding XSLT General Params into ForEach
If you tried to add an XSLT General Params object into the ForEach form, IWS would error and close. The code was updated to resolve this issue.
This issue was tracked as Item #123122.


Issue From Different Parameters In Sub Worksheet And Empty Parameters in Parent
Worksheet
If you dropped a Source grid (or other object that leverages its parent settings) that had different parameters inside any sub worksheet (for example, a translator Group sub worksheet), there was a possibility that IWS could error and close. This issue could occur only if there were empty parameters in the parent worksheet. The code was updated to resolve this issue. IWS now correctly handles empty settings in the parent worksheet in these instances.
This issue was tracked as Item #123125.

  • No labels