...
Currently, you will only need to uninstall Integration & Workflow Studio (toolstest.eagleaccess.com). After the May 13th push to IWS Production, you will need to uninstall IWS (tools.eagleaccess.com). To reinstall, you will need to use the new URL for the IWS Test Toolstest site: https://toolstest.eagleaccess.com/iws45/index.htm. A new URL for the IWS Prod Tools site will be supplied on May 13th.
This issue was tracked as Item #124965.
...
If you set focus on any destination or source cell in IWS and then used the Alt+Tab command to switch to another window, when you went back to the IWS window you were not able to click on the script bar. The code was updated to resolve this issue and the scriptbar area will now preserve its focus if you switch between windows.
This issue was tracked as Item #128110.
...
If you used a XSLT ForEach object with a child ReasonCheck node in a XML to EagleML translator and have do not have any ForEach objects connected with transaction destination node, the Reason node may be not wrapped into 'xsl:for-each' elements on export. This issue would cause incorrect relative path processing. The code was updated to ensure that ForEach elements are no longer skipped in this case.
This issue was tracked as Item #129077.
...
In some cases when you resize a column in Data objects or any Lookup-like object, the entire shape was moved to the new mouse cursor position. The code was updated so that mouse clicks are now correctly processed in grid header area.
This issue was tracked as Item #129860.
...
If you clicked on Open XPanel, clicked on the Refresh Extension list and quickly tried to close the dialog box, IWS could close unexpectedly. The code was updated to include a check for the selected panel to update the list of extensions before closing.
This issue was tracked as Item #129924.
...
If you clicked on New File from then Solution Explorer tree and after choosing a Source and Destination and clicking OK, you closed the dialog box while the files were being uploaded, IWS would close unexpectedly. The code was updated to address this issue.
This issue was tracked as Item #129964.