Initially released to IWS Test on 20150603
Enhancements
New Preprocessor Object in Worksheet Tab
A new MC Preprocessor object has been added under the Activities section of the toolbox in the Worksheet tab. You can use this object to perform specific Message Center preprocessing activities.
This issue was tracked as Item #129914.
Software Fixes
Remaining Issues Around Viewing the latest EagleML in Existing workflows
The ability to refresh the latest EagleML in an existing workflow was addressed in a recent release. However, there were still a few issues remaining that have now been corrected. These issues included:
loss of conditionToinclude mappings
loss of some direct mappings
loss of some hard coded values and mappings when using the refresh button
.
This issue was tracked as Item #130673.
...
When you deleted an existing object in the Worksheet tab, you were not able to recover the object using the Undo option on the toolbar. The code was updated so that the object's properties are saved prior to it being deleted, allowing it to be recoverable now. Note:
| Info |
|---|
The item needs to have been recently deleted, as the Undo option allows you to undo up to the last three actions only. |
This issue was tracked as Item #130593.
...
In v1.01.401, the PaceJob and StarJob Objects renamed to Eagle Warehouse and Eagle Accounting. However, some of the underlying properties of these objects still had the older nomenclature. The code was update to correct this. In the Eagle Accounting object, theproperty STAREventName was change to EagleAccountingEventName. In the Eagle Warehouse object, the property PACEEventType change to EagleWarehouseEventType and the property PACEEventName was change to EagleWarehouseEventName.
This issue was tracked as Item #130697.
...
When creating a Generic Extract, if you populated the Extract Name Pattern with a value and then closed the extract, when you reopened the extract, this value would be lost. The code was updated to ensure this value is preserved.
This issue was tracked as Item #130460.
...
In the Transform and Generic Load template, the Map Full Message will now be checked by default only when you select XML as the source. This change is related to similar changes made in v1.0.1.401 around the default setting for Map Full Message.
This issue was tracked as Item #130836.