IWS Release Notes - Version 1.0.1.607

Initially released to IWS Test on 20160422

Enhancements

Improvements to Task Extractor

The Task Extractor was improved. The current version allows you to set control message parameters as source and Stored Procedure or SQL DB request as destination. In addition, the Input Parameters and Workflow Parameters translator objects were added to set input and output parameters. With these changes, you don't have to manually add EJM includes and needed parameters. Also, the new DB Request destination form allows you to configure request and its parameters in a more user-friendly way. Eagle plans to continue to simplify the extractor process in upcoming releases.
This issue was tracked as Item #140660.

Software Fixes

Files Missed After Importing/Exporting Solutions

When you exported a solution, there were times when not all the components actually were included in the solution bundle. This resulted in issues when you then imported the solution to another environment. This issue was not obvious and therefore could cause you significant time triaging what the underlying problem was. To resolve this issue, the solutions export algorithm was improved. IWS will now detect missed files from package on import step. IWS is now able to import MC package with default structure.
This issue was tracked as Item #140855.

Remember the Last Used Import and Export Paths

In a previous release, we introduced some functionality to remember the last used information for import and export solutions. With this change, feature worked as expected for imports as IWS remembered the last import path. However, there was still an issue for exports. It would keep the exported path only under the same session. If you closed and reopened IWS, the path was lost. The code was corrected so that IWS will now remember the last used import and export paths even after you have closed and reopened IWS.
This issue was tracked as Item #140857.