Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expression editing features were added to the Generic Extract properties form. Text fields now have an Expression mode toggle button that allows you to use Message Center syntax text check, word completion feature and automatic character escaping.
This issue was tracked as Item #129662. 

...

A new workflow validation feature was introduced. This initial release of the validation includes check for missing connections between most Events, Activities and Gateway objects. A warning message with a cancel option will be displayed when saving or exporting invalid workflow.
This issue was tracked as Item #129938.

...

The latest EagleML additions were not being displayed in existing IWS solutions. This issue occurred even though IWS referenced the XSD that included these changes. The code was updated to address this issue. In an existing workflow, to see new fields, you will just need to go to the destination grid and select the Set Destination on the bottom left corner and then reselect the specific EagleML (for example EagleML-2-0, SMF, Generic SMF). This action will then bring in the latest additions. Your existing mapping with not be affected by this action and the new fields will be available to map.Note:

Info
  • If you do have expressions from optional EagleML models, the model must be in an expanded state before updating. If it is an a collapsed state, duplicate expressions may appear. (This is a known issue that is being addressed in an upcoming release, tracked under #130217.)

...

  • Eagle plans in a future release to simplify this process further by adding a Refresh button.

This issue was tracked as Item #130233.

...

If you changed the width or height of a resizable object, it could be reset to the default size after re-opening the translator. The code was updated to resolve this issue and the objects' sizes are now saved with solution.
This issue was tracked as Item #130110. 

...

IWS did not always properly detect the subprocess type. This gap could cause issues with the workflow script files. The code was updated to detect Message Center based processes, set the correct type for added subprocess and create the appropriate the workflow script files.
This issue was tracked as Item #130075.