IWS Release Notes - Version 1.0.1.342

Owned by Former user (Deleted)
Last updated: Sept 04, 2024 by Kinga Huszno
3 min read

Initially released to IWS Test on 20150121

Enhancements

Simplifying Header and Footers Handling
Enhancements have been made in IWS to simplify the handling of header and footers. For Delimited or TagValue source formats, you can read information from headers or footers now by simply enabling the 'Parse info from header lines' and 'Parse info from footer lines' checkboxes in the Task Format form and dragging the new 'ReadHeader' and 'ReadFooter' objects to the worksheet. You can also create headers or footers for Delimited or TagValue result message using 'MakeHeader' and 'MakeFooter' objects. These new objects can be found in the Special objects ToolBox section.
This issue was tracked as Item #123933.


Added Generic Extract and Transform Object
A Generic Extract and Transform object was added to the ToolBox, under the Generic Extract and Transform section. This object provides the same functionality of creating a custom Extract transformation stream as with the Generic Extract and Transform Template. The task for the transformation stream can be created and opened using the open option in object's context menu or by double clicking.
This issue was tracked as Item #126575.


Added ReasonCheck
The new object 'ReasonCheck' was added to out XML translations to apply a ReasonCheck node. This object is available under the Special section in the translator toolbar. With ReasonCheck, if the expression in the condition is evaluated to true, then an XML node 'reason' will be added to the output. Here is a sample of the XML output:

<reason> <reasonTypeEnum>WARNING</reasonTypeEnum> <reasonCode>-1001</reasonCode> <description>Something wrong with IssuerID value</description> <reasonTag>1</reasonTag> </reason>

This issue was tracked as Item #126586.

Software Fixes

Unnecessary Error Messages When Opening XML rules
If you try to open an XML rule in 'File System' mode, you could get multiple error messages about failed open attempts of overlay include files. The code was updated to resolve this issue. These error messages are no longer displayed as these files are optional.
This issue was tracked as Item #122890.


Preview Window Missing Name in Window Title
When you previewed an export, the preview box simply had the generic title of 'Preview'. The code was updated to that the selected solution item name is now included in the window title caption.
This issue was tracked as Item #125787.


Issue with Exporting Router Rule for XML Messages
If you created an outbound task with XML source format, you could get an incorrect expressions for data separation attributes in the exported router rule file. The code was updated to resolve this issue. The attributes for root and message nodes settings are generated correctly now.
This issue was tracked as Item #126083.


Changed Order of PaceEventType and PaceEventName
The PaceEventType and PaceEventName properties of the PaceJob object were in the wrong order. The PaceEventType should be listed first, since the PaceEventName property is associated with the PaceEventType you select. The code was updated to resolve this issue. The PaceEventType property is now listed before the PaceEventName property.
This issue was tracked as Item #126461.


Unnecessary PaceEventNames Values Available in DropDown List
When you have a PaceJob object on your workflow, you need to populate the PaceEventType and PaceEventName properties. The dropdown list for the PaceEventNames showed all possible values instead of limiting the values shown to those associated with the PaceEventType you selected.The code was updated to resolve this issue. Once you select the PaceEventType, only the values associated with that type will be listed in the PaceEventName dropdown.
This issue was tracked as Item #126462.


Issue When Decision Control Flows into Fork

If you had a workflow that had a decision control object and its next step in the workflow was a fork, IWS would generate an invalid workflow (.wrf) file. The code was updated to resolve this issue. IWS now properly handles this condition.
This issue was tracked as Item #126513.