IWS Release Notes - Version 1.0.3.57

Initially released to IWS Test on 201804027

sprint 3.5

Bug Fixes

 

Issue switching between "Data Settings" and "Structure" grid

Switching from Data Settings to Structure Description and then back would clear all the unselected models from "Data Settings".
The issue was fixed by correcting the logic in the merge method for grids.
This issue was tracked as Item IWS-419.

 

Failure tolerance.

IWS generated all stream with Failure tolerance=100.
The default value 100 leads to the situation when the "step" of the EJM workflow is shown as success, but underlying message can be failed.
The problem was fixed by changing the default value for this parameter to 20.

This issue was tracked as Item IWS-293

 

Incorrect execution order

When you use variables in expression, parent object is always placed after all variables initialization if connection line was not manually removed.
That could cause incorrect rule elements execution order for expressions that use global variables.
The code was updated to resolve this issue, global variables no longer affect elements execution order.

This issue was tracked as Item IWS-318

 

MT - sorting by Record ID
Sorting by record ID in the Message Detail tab did not work properly.
The issue was fixed by applying "numeric" sorting algorithm instead of "string"

This issue was tracked as Item IWS-321

 

Issue with extension export

Export functionality in XPanels returned error at building extension in export tree.
The problem was fixed by fixing logic for changing main EagleML xsd file when reading extensions from xsd (add reference to "eagleml-custom-2-0.xsd" file).

This issue was tracked as Item IWS-421

 

Enhancements

 

Variable shape in Python-powered streaming translators

Variable object was added to the Tool Box of Python translators. the feature is similar to the MC variables, but only local variable scope is supported.

This issue was tracked as Item IWS-332

 

Convert to XMLDBAPI Python translation parameter

In previous versions all Warehouse models always produced XMLDBAPI output in Python translators.
This can now be customized in new ConvertToXMLDBAPI parameter of Destination grid.
The feature is available for Warehouse objects group only and is enabled by default for Open Lot and Position models.

This issue was tracked as Item IWS-422

 

Support for 'User' EagleML object

New 'User' and 'Group' types have been added to the EagleML models list in IWS data objects, Generic Extract form and XPanels.

This issue was tracked as Item IWS-426

 

EBS and IWS integration

Some refactoring work has been done to allow usage of EBS-style controls within IWS in the future

This issue was tracked as Item IWS-412

 

Multiple incoming file in streaming tasks.

The streaming tasks in IWS could not process more than one file.
The code was changed to allow processing of multiple incoming files.

This issue was tracked as Item IWS-258

 

Warnings on Run in case the stream is invalid

IWS executes streams via exec_wkfl process, and in some cases, if there are problems with the underlying stream, it could return incorrect error message or return empty message.
"Test stream" has been added before the "Run" command in order to validate the stream before its execution
Now, if there are issues with the stream to be run, proper warning/error will be displayed.

This issue was tracked as Item IWS-50

 

move Refresh solution cache to expert mode

"Refresh Solution Cache" should only be used in very specific cases, and can be confused with "Reinit Cache" button.
To avoid possible misuse, we moved "Refresh Solution Cache" button to the expert mode inside IWS.

This issue was tracked as Item IWS-357

 

Raw Service - handle changes to the schema

In the past, new structure name would be created on each publish action, even if the structure did not change.
It would make previously loaded data difficult to retrieve.
The issue was fixed by storing structure content, and tracking the changes before subsequent publishes.

This issue was tracked as Item IWS-424