Flynet Viewer Studio Installer 42o

Enhancements and Fixes for Flynet Viewer Studio since installer 42M

Flynet Viewer Studio (Build: 4.1.2.40212)

Web Service Generation and Testing

• Added new Task context menu item: “Run a Generated GUI Unit Tester” which will display if a GUI Unit Tester solution already exists for a Task.  This allows running the GUI Unit Test for the task without the need to regenerate.
• Menu option to generate new code for the GUI Unit Tester changed from “Test Logic with a GUI Unit Tester and live host connection” to “Generate and Test Logic with GUI Unit Tester“.  This is to more clearly differentiate this option from the new menu item, “Run a Generated GUI Unit Tester”
• The OnTaskError and OnTaskCompletionoption properties for a TaskScreen are now displayed and utilized for both Pooled and non-Pooled sessions.  The generated logic for the GUI Unit Tester was not controllable without this change for non-pooled sessions.  This change is one of a number to improve support for chained task testing with the GUI Unit Testers.
• Reload button added to GUI Unit TesterInput parameters tab for tasks defined with Inherit navigation (uses sessionKey to connect to an existing session instead of running a HostLogon).  This allows testing multiple cases without having the reload the tester.
• New Task Wizardwill no longer disable the Auto Selection option for a screen if the screen doesn’t have Navigation type of DrillDownList (which it did used to do).  This avoids the need to set a screen’s navigation type to DrillDownList when it is not always used for navigation (for inquiry, for example).
• Added the MaximumEntryRetriesto a TaskScreen with “Add New Data” as the TaskIOType.  If an Add New Data screen is included in the EntryOKScreens (meaning that an enter could stay at the same screen), MaximumEntryRetries can be set to a positive integer valueto indicate how many times the Add New Data operation will retry entering as long as the screen has not advanced to a different screen in the EntryOKScreens list.�Useful in situations where a user needs to keep entering “clear” or “cancel” into a screen until a set of conditions is met, such as reading all errors from a queue.
• Generation of a GUI Unit Test application now supports selection of the Visual Studio target version (VS2005 or VS2008) with the default being VS2008, if .NET Framework 3.5 is installed.  Setting this property will persist for the duration of a Studio Session (next time Flynet Studio is opened, the property will be VS2008).

Miscellaneous Fixes

• The TaskScreen TaskIOType, ReadAfterWrite and ForceOverrideNavigation properties were not setting the “needs saving” flag when changed, so that the user would not be prompted on closing an application to save if only these properties had been changed since the last save.
• FieldFilter Editor, used in properties such as the TaskScreen WriteFilter was displaying an exception messagebox (not affecting the state of Flynet Studio) if a Field included in the filter as an omit/include had been deleted or had its name changed since the last edit of the filter.  In this build on editing the Filter, the entry for the changed field will be discarded and the field will need to be reselected for filtering.
• For Finite-State web service tasks, a multi-row field map screen was breaking a task into multiple parts if there were any recorded actions indicating the screen had drilldown list characteristics.  Drilldown list now needs to be explicitly defined in the TaskScreen for this behavior (it is no longer auto-detected for Finite State web services).
• Adding the MaximumEntryRetries property enabled the avoidance of unwanted recursion back to the same Add New Data screen when enter-retries were not expected or desired.
• The OverwriteWebConfig property for the Web Service Generation Wizard was fully implemented to trigger a replacement of the web.config file when the property is set true.
• The Zip managementlibrary was upgraded from Ionic.Utils.zip.dll version 1.5 to Ionic.Zip.dll version 1.8.  This is used for exporting application archives as well as GUI Unit Test Export/Import operations.
• GUI Unit Test generation no longer ignores a “No” answer on the confirmation of clearing the contents of the existing folder if the user had checked the “Clear any Existing Code” checkbox.  User was unable to cancel or prevent the clear if the checkbox was checked by accident, or left checked from a prior run.
• GUI Unit Tester status window no longer closes automatically if there is an error during the generation.  Error messages reporting why a generation failed were being cleared too fast to read.  The GUI Unit Test generation window now only closes automatically on a successful generation, compilation and display of the newly created GUI Unit tester.
• Pooled session input names, used in the creation of the encrypted credentials file and Editor, were not being generated using a full traversal of all possible logon screens.  In certain scenarios of recordings, this was creating the wrong list of possible screens and parameters.
• Single screen Tasks in web services, when the same screen in add new data was defined in the EnterOKScreens list, were generated with a loop in the state handlers, such that the do[screenname]Result state was called by the do[screenName]OK state, which produces a loop, as the do[screenName]OK state in a single screen task should return a doReturn state handler request.
• Duplicate state handler names for do[screenName]Except were being generated when the same screen was defined as both and Add New Data and Auto-Selection in the same Task.
• The ParameterOverrides property for a TaskScreen was not always finding a match in the ASMX.cs method’s parameter list, due to a few mismatches depending on the Task IO Type.  Also fixed cases where a leading comma in parameters would cause a compile error.
• The ParameterOverrides property was not warning on a spelling or case mismatch with a generated parameter.  A warning is now issued if a defined parameter name in the ParameterOverrides property is not found.
• Comments and NextScreen “wait for screen” list had many duplicates in environments with a large number of recorded screen changes for the same from-and-to screen.
• Compile errors for UI solutions under certain circumstances (regression) was fixed
• Auto-selection multi-row fieldmaps that used matching field names to enter a row value into a default fieldmap entry field was fixed to use the SetText instead of the trySetText method of the HostScreen (oScreen) class object, causing problems with the compile (regression from implementation of TrySetText to improve data entry outcomes for dynamic screens).
• web.config for Web services now points to the FVTerm virtual folder for the Emulation path, reflecting a change from SCTerm for the installed virtual folder
• WriteFilter for an Add New Data or Edit Data task screen had the “Click on a Field Name in Treeview…” label anchored to the top of the form instead of the bottom, so that if the form was resized to be taller, the label would appear over the controls normally situated above it.