These builds for both the Emulation Service and Studio feature both enhancements and bug fixes, along with a new installer for the base product that manages MSI upgrade issues.
Flynet Viewer Base Product and Components (Version: 4.1.20)
New Installer – FVSetup.exe (replaces FlynetViewer.msi)
- FVSetup.exe is an MSI wrapper that ensures that the correct version of Windows Installer is available (and upgrades if not)
- Automatically performs upgrade of existing installation, retaining all registry settings while replacing all installation files
- Fully tested from minimal Windows/XP install
- Upgrades to Windows Installer 3.1 if 2.x installed
- Provides guide to install .NET Framework 2 SP1 if .NET 2.0 is not installed
- Requests installation of IIS if IIS component is not installed
- Guides activation of ASP.NET if not active for IIS
- Detects and provides guide to installation of Microsoft Management Console 3.0 if not installed
Flynet Emulation Service (FlyServer.exe)
- SCO-ANSI terminal type support added for VT–still requires registry setting for the actual Telnet terminal type (configuration select-VT) to match active host termtype. Included support adds 1) host macros, 2) SCO color commands and 3) SCO keyboard lock/unlock
FVTerm – Flynet Web Terminal Emulator
- Added VT220 support so that reliable recordings can be made in a VT environment. Note that the use of keyboard definition files works. Custom keyboard setups (CustVTKeys.dat in Definitions folder) can now be supported as are frequently encountered in many older Unix applications
- Improved display of the AID key(s) when viewing a recording. Location and size are improved, and long key strings are supported, which may be encountered in a VT environment.
- Improved usability of the Recording Viewer–page-up and page-down as well as the mouse scroll-wheel are now supported, with improved management of the elevator scroll element.
- PA1 and PA2 keys were added to the recorder (Ctrl-F1 and Ctrl-F2)
- Terminal Emulation had extended color foreground and background attributes backwards–fixed so that colors in extended environments are correct.
Flynet API Library (ViewerLib.dll)
- New trySetText method–same parameters as the setText method, but will ignore a null text parameter as well as attempts to write to a protected screen field; returns a true if writes successfully, false if one of the above prevents writing. If the active screen is an unformatted 3270 screen, will perform a putKeys() method and return true.This new method was introduced to better support screen write methods in web services, where a null parameter is accepted as a “don’t write this” and where a host dynamically changing a field to protected shouldn’t break logic on its own.
- SCO-ANSI host-sent macros now supported with the getHostMacro() method, which will return a host-sent macro command or null if none are pending. Keep calling until any pending macros are all read.
Flynet Viewer Studio (Build: 188.8.131.52001)
New Recording Import Helper
- Activated with right-click on Recording (Import/Import New) – provides small modeless window that displays the next unrecognized screen in a recording and simplifies the import, naming and recognition of the screen.
- Get Next button rapidly finds the next unrecognized screen in the recording and imports it
- Automatically runs the Check Recognition scanner detailed below
Check Recognition for Popups and Overlays
- Separate recording analyzer that verifies the existing recognition through all of the screens in a recording
- Final Validation scanner–scans for recognition anomalies to locate popups and overlay screens so that they can be imported and recognized accordingly
Screen Heatmap Display
- Great for analyzing how a screen is used throughout all the recordings
- Right-click a Screen Definition – Display / Display Heatmap
- Current screen display changes to a “heat map” of host screen writes and user data entry, color coded to show which portions of the screen are changed the most
- Scans all associated recordings to produce the source of the heat map
User Navigation Definitions
- New facility for user-defined navigation between screens without the need to specifically record the navigation
- User Navigation Dialog opened with right-click on Screen Definition (Modeling / User Navigation) or in the Navigation view in the “To” list (Add new User Navigation; Override with User Navigation)
- Displays the “from” screen in left pane with thumbnails of possible “To” screens on the right, color coded to match any known navigations.
- User clicks on a “To” screen to add field changes and the Enter key
- A new field change can be initiated with a button or by clicking on a location in the “From” screen view
- User navigation definitions take precedence over any recorded changes and are used in the generation of the navigation code for web services and other generated applications.