Flynet Installers 42T

Enhancements and Fixes for Flynet Viewer Emulation Service and Flynet Viewer Studio since installers 42P featuring:

• 64bit Windows Support
• New Multi-Recording View for Recorder 2.0
• Search and other options to improve viewing recordings
• Table-based Screen generation for the UI generator

Flynet Viewer Base Product and Components (Version: 4.1.38)

Windows 64bit Installer

Starting with Installers 42T, a native 64bit version of the core emulation service will have a setup provided. Without a native 64bit version of the core service, there are compatibility problems, particularly when needing to integrate with other native 64 bit applications.

The installed ViewerLib.dll assembly (installed to the Global Assembly Cache) also contains native 64bit c++ code to integrate with the service.

Generated Flynet applications are pure .NET and will naturally connect and utilize the 64 bit or 32 bit versions of the emulation service.

To function correctly on a 64 bit platform, Flynet Viewer Studio must be installed at 42T installer level or higher (along with the FVSetup64 of the emulation service).

NOTE: at the 42T level, the tray icons are not yet supported in a 64bit environment due to ancient MFC code that is not moving well to 64bit–the Flynet Administration and Simulated host control must be performed from the Start button Flynet Folder.  We expect to restore this functionality in the next build.

Flynet Emulation Service (FlyServer.exe)

A few enhancements and fixes:

• Fix: when a host IP fails to connect, the initial DNS name is rechecked to obtain a new IP address.  This fixes environments where network connections can recycle the connections across VPN or other connections. 
• Fix: on multithreaded systems, a tight loop acquiring new sessions with the HostConnection.Connect method could result in two threads to obtain the same session when the host initialization (telnet handshake) is slow.
• Fix: setting long active user (HostConnection.owner) strings could cause invalid state in a session
• Fix: html reserved characters were not being escaped in the HostConnection.owner string when sent to the console, causing display issues when an owner contained html reserved characters

FVTerm – Flynet Web Terminal Emulator

• Enhancement: for custom start pages (replacing SCTerm.html), a custom “welcome” page can be set by including a javascript variable definition.  For standard emulation environments the welcome page can be set with the variable named “welcomePageName” and for SharePoint web part environments it can be set with “welcomeSPPageName”.

Flynet Viewer Recorder 2.0

• Multi-Recording mode implemented.  Allows more than one Recording to be viewed in a sorted-categorized view.  For situations where the Telnet Recorder has been used to record a worker that uses more than one terminal emulator to perform his or her job.
  • When selecting a recording to view, can now use multi-select actions (shift or control-click) to select more than one recording
  • Will sort individual screens from the multiple recordings and present them in a visually organized view
  • Requires latest build of the Telnet Recorder (http://www.flynetsoftware.com/42T/FTRSetup.exe) to ensure synchronized timestamps in the recording file
• Tool Strip in the Recordings viewer added which includes
  • File – Add another Recording (for multi-view)
  • Search – Search in Recording
  • Search – Repeat Search
  • User Keystrokes – Auto display (will show the changes to a screen without needing to click the animation button)
  • User Keystrokes – Animate during play is now selectable

---

 

Flynet Viewer Studio (Build: 4.1.2.40275)

Integrated Development Environment (IDE)

• Support for integrated registry values for 64bit installations of the core emulation service
• Web Preview fixed to support non-standard characters and other issues with new Table and Div generated pages
• Heatmap includes the cursor location (dark orange body, dark blue border) when viewing individual screen images (browsing)
• Fixed issue with screen resizing of the main panel (center), where in many circumstances the bottom or right portion of the screen was clipped, requiring a resize operation to fix the dimensions so that the bottom or right portion became visible.
• For Popup Screen definitions (IsWindowPopup=true) with the property floatingWindow=true the recognition in the runtime and the recordings analyzer inside FV Studio was improved to support overlapping popups and stacks of popups
• Navigations Tab had inconsistent control of the vertical panels as well as sizing of the screen (fixed)

Log Viewer (from Tools menu and inside GUI Unit Tester)

• Search function–provides ability to find text anywhere in the log

Web Service and UI Generation and Testing

• For MultiRow Fieldmaps, new properties to control PageUp and PageDown operations in generated applications, PageForwardKeys and PageBackwardKeys which allow an override of the project definition for these keys for a specific screen’s multirow fieldmap.
• Runtime TaskSession object enhancement–added the SetLogName method, which allows the active log name to be set by other classes following initialization.  This makes customized log names easier to implement.
• Some fixes to navigation in the logon, logoff and navtohomescreen method generation templates
• State logic modules for web services had some inconsistent status being returned in the Info object “lastStateHandler” property
• State logic modules are now generated so that the base class Start and other entry methods are virtual and overridable in the user enhancement class
• Runtime logging in VT environments has better “before” and “after” screenshots, as the before was missing the user keystrokes that update the screen prior to entering it
• Data entry for VT environments updated to better support auto-skip fields and updating existing data; will efficiently generate and at runtime support updating fields where existing data may be longer then the updating data, and where autoskip is present on some but not all fields
  • FullBlankPadding property added to a field for CharacterMode definitions, to indicate when blanks are needed to wipe existing data (assumes non-destructive tab) –this is defaulted to yes
• Heatmap view would cause exception if no recognized screens found in any recordings for the definition clicked
• Heatmap cosmetic fixes for title area, and protection added against exceptions due to unpredicted recording state

UI Generation

• New table-based web page generation option added which provides better compatibility with Visual Studio 2005 and 2008 (which have progressively moved away from good WYSIWYG support for absolute positioning).
  • Provides much better HTML rendering of complex screens with no overlap of fields or large areas of white space
  • Set the Screen definition template to Panel Divs
  • Define at least one Panel using the Panels node in the screen
  • Recommended that you define panels from leftmost to rightmost column, trying to align with the natural flow of the columns on the page
  • One big panel can be used but on complex screens, this will result in one table that has very complex colspans
• Panels have been set so that the default template generates tables inside of the panel DIV tag
• The FloatingDivs template is still available for Panel nodes as a setting for the PanelTemplate property–this template requires more work to get a page to render like the original screen than the table template (comment–tables are better for reproducing complex form layouts!).
• List controls for runtime UI environment had HTTP caching turned off for better consistency of the runtime ASP.NET UI
• When assigning a function key to a button in the Actions collection of a Screen definition, the PF13 through PF24 keys were not being recognized at runtime.  This was fixed with a few changes to the FVChildWindow.js file for the ASP.NET Runtime.
• When a multi-row list is selected by setting the value of a field on the screen (instead of an action column in the list), the single-click and double-click actions for the ASP.NET control were not working correctly.  A setting was implemented whereby the Single or Double click action properties in the list control can be set to “*key1” or “*key2” to return the value of a key column in the row instead of a fixed action like “1” or “7”…
• Code-behind for a mapped list was not correctly setting the name to call on a click action for lists with separate fields to set instead of an action colum within the list…code behind was calling “MappedList_Enter” instead of a specific method using the fieldmap name as part of the method name.
• List class for multirow fieldmaps with a KeyColumn drill-down type (copy key row field’s value from row to a matching-named field in the default map) was not implemented in the user class
• Generic Menu template was not rendering in Web Preview and also had issues in some screen formats
• Some templates were updated to be more XHTML compatible as a move to full XHTML compatibility some time in the future