Inventu Viewer+ Software Updates

• VT FVTerm Terminal Emulation now supported on Touch Devices
• Improved general Touch Support for FVTerm
• New ability to configure FVTerm web.config from high level UI

Flynet Viewer Base Product and Components(Version: 5.0.32)

Emulation Service Setup on 64 bit systems

• On a 64 bit platform, the 32bit FVSetup.exe will now refuse to install and display a message for the user to run the FVSetup64.exe on a x64 platform.  Before this fix, running the 32 bit installer on 64 bit systems displayed the “IIS not installed” error during setup, no matter how many times IIS was verified…

Flynet Viewer Emulation Service (Version 5.0.32)

• Bug fix–for TN3270E extended terminal type IBM-3278-2 EAttrs, the device RPQ data incorrectly indicated support for Programmed Symbols
• The older, HTA based recorder–when generating a definition, all screen XML elements have the treatAsDefault set true so that when the definition is active, the emulator doesn’t send control to an assumed UI controller.

FVTerm Web Terminal Emulation Feature

• New Administrator’s Configuration web page added. This makes it easy to apply certain changes to the web.config file without the need for editing. Included is the ability to select which defined hosts to present to users for the connection menu, the default host, whether connecting is automatic or user driven and so on. Also included is selecting between Windows security for user identification or macro-based.
• Fully documented and fully implemented a parent-window javascript support class. This makes it easy to initiate or connect to an existing session then have control and be able to capture events. See FVTermParent help.
• Initial support for in-place field upgrades has been implemented. This is currently setup to enable displaying a “tool tip” for selected fields to provide immediate help. Future releases will include the ability to replace an input field with dynamic selection lists, radio button pop-ups and so on. This is based on the label for the field not specific screen or location.
• AS400 menus that have a “primary” on the left and a “secondary” (like a popup) on the right are now supported for clickable selection.
• The PA1, PA2 and CLEAR keys will now SEND when the keyboard is locked. These keys were being buffered like other keys and for long-running applications that the user is accustomed to “breaking” with a PA1, PA2 or CLEAR key it was not possible.
• On touch devices, optimized auto-scrolling of the screens when the virtual keyboard is displayed–this is in addition to the support by the device for the active input field.
• Touch device ViewPort setting optimized for better pinch-to-zoom support so that users can start with a 1-1 view and zoom as needed.
• For VT devices the “beep” or alarm is now cross-browser (it was using an IE-only technique to play the sound)
• Suppressing auto-skip on iOS devices as this causes the virtual keyboard to close–it is easier for the user to click “next” than to have the keyboard disappear and need to be reactivated.
• Tweaked support for numeric-only entry fields. Currently supported on iOS touch devices only for activation of numeric virtual keyboard. Other touch devices have problems with type=”number” for html input fields.
• Clipboard paste using menu or a tablet’s built-in paste function was not copying data when in native web field mode.
• Added support for VT protocols on non-Android touch devices. Android web browsers do not support the onkeypress event which is essential for virtual keyboard support when not presenting traditional web fields. Tested and supported on iOS and Windows 8 devices.
• Improved full-duplex keystroking performance on VT emulation by reducing the actions taken in the status bar on single keystrokes.
• When loading the emulator with a URL, can now include a specific Application Name for the session (&Application=name). The application name is used to match a screen recognition and mapping definition file to enable high-level recognition and field mapping.
• Minor bug-fixes in macro generation and window management, improving screen identification and runtime control.
• Improved support / fixed some visual bugs so that loading of the ActiveX keyboard is guided and more consistent for new users connecting for the first time (only applicable when customers have included the ActiveX support)
• Bug fixes and enhancements for pinning the function key images based on landscape or portrait mode — now is defaulted for new users on touch devices to have the function keypad displayed.
• CSS fixes for some browsers that were displaying input fields with additional borders. Also for touch devices to prevent auto-complete and spell check / other keyboarding properties not applicable to terminal data entry.
• Preload key images to improve performance in the iPad for keyboard display
• BlackBerry Playbook support re-instated

Application Log Viewer

• Exception occured with custom logs for parameter lists that had a blank line

Microsoft Management console Plug-in

• Session status between started and stopped was not always refreshed automatically, requiring an explicit refresh action to accurately reflect which sessions were stopped or active.

Flynet Viewer Studio (Build: 5.0.0.33)

Studio User Interface

• When a field name had a length conflict, when the name or length was changed (and conflict was fixed), the icon would remain red in the treeview–icon will now go to normal color once the length conflict is corrected.

Web Service and UI Generation

• For pooled session credentials, the ENC file and Credentials Editor now support multiple pools (different userid/passwords based on pool) as well as unique userid/passwords by session. In past versions, unique userid/pW combinations were supported on a session-by-session basis but only by entering all userid’s and passwords on one line separated by blanks.
• Encrypted Credentials could have null characters appended to values, which could cause the editor to warn about changes that had not occurred.
• Generating Strong-named assemblies on machines with .NET 4.0 toolkits had an error in the path to the SN.EXE program used to generate keys so that the project/solution would generate but the keys would subsequently need to be generated in Visual Studio to build the solution.
• MSBuild on x64 platforms now run as x64 to avoid problems IIS not including the correct assembly references
• For Web Project based generations (not web site), the target site was defaulted to “Default Web Site” even if a different website was selected during generation. Also, the port was not included in the project reference so that if the Default Web Site had a binding for a different port than 80 (common on SharePoint servers), the project would not load. The selected web site is now used, as well as the selected web site’s listening port.
• For pooled sessions, generation of the HostLogon and other navigation methods would have problems with setting the initial screen displayed as the home screen.
• Debug Builds were targeting the bin folder instead of bindebug in the folder tree, which caused copy issues

Web Service Generation

• Test Case Generation now provides the ability to identify multiple home screens, like 3270 transaction screens and clear screens when a transaction can be triggered from either. This provides better matching of test cases and tasks for the GUI Tester.
• WCF Client testing files were using the Google CDN for Jquery javascript and CSS files–this caused problems on locked-down servers that did not have access to the outside internet (including Google).  All jquery resources are now installed in the web service IIS application folders.
• The Task and Project Visual Studio / Find All Changes action was not detecting a changed [taskname]Info class if the User Task region was not also changed also.  This has been corrected so that the [taskname]Info region has changes, they will be detected every time.

Simulated Host Script Generator

• Multiple recordings with different data through same screens had context issues making some routes non-reproducible – fixed so that multiple cases more reliably supported for testing
• When the first screen displayed was the alternate row/column configuration in recordings, the Simhost script was incorrectly generated

• All new look and user experience for FVTerm Web Terminal Emulator
• FVTerm now supports any touch device, including iPads, without a separate HTML top page
• Windows Security / User Identity integrated with FVTerm Macros and Extended/Custom session logging
• Windows Communication Foundation (WCF) Generation Option for Web Services
• jQuery AJAX Compatible JSON Web Services with the new WCF option including a test HTML harness and Sample Code for individual Task calling
• Integrated Generation options for Visual Studio 2012 and .NET Framework 4.5
• New Installation Videos for Windows 8 and Windows Server 2012 as well as Windows 7, WS2008, Windows/XP and WS203

Flynet Viewer Base Product and Components(Version: 5.0.27)

Emulation Service Setup (FVSetup.exe and FVSetup64.exe)

• Setup and Flynet Viewer Studio IIS API is now based on either IIS6 or IIS7 style API depending on which is available.  No longer need the IIS6 API feature active.  Setup now installs FVTerm as a .NET Framework 4 application as well as managing the FVTerm v4.0 pool
• Production (access codes) Keys now require verification of active maintenance to install a particular version.  Customers that do not have active maintenance can still use older versions but will not be able to upgrade to versions with a creation date that is later than the end-date of the maintenance.  This is achieved during installation and execution with an HTTP call to http://flynetworldwide.com.  If a production server cannot access via HTTP, the FVLicense.exe utility can be downloaded from FlynetSoftware.com and run on a administrator’s PC to create a special license verification file that is copied to the production server prior to running the new FVSetup on the server.
• The FVTerm install will no longer replace the web.config with a new one–the old web.config is saved during the install process and may be upgraded to add new application elements not previously in use.  The SCTerm.html file is also kept but as SCTermbak.html as the new version requires changes to the hosting HTML layout and javascript.
• A separate installer for the MMC is available–FVMMCSetup.msi

Flynet Viewer Emulation Service (Version 5.0.27)

• The [backtab], [delete] and [home] keys were not properly interpreted in VTxxx emulation
• Administration tools updated to accomodate magnified screens / alternate DPI modes
• Admin Console right-click now activates the session actions instead of the browser actions
• Added a few more VT Terminal types to drop-down in Host configuration
• 3270 Protocol fixes for compression and send-changes-only writes that were breaking the internal attribute structures
•  

FVTerm Web Terminal Emulation Feature

• All new background graphics and icons in bottom status and tools bar with higher quality (especially at larger sizes) and clearer association between the image and the action when clicked
• Touch mode devices have larger, easier to press action icons–this is no longer specific to iPad but any touch-capable browser
• New FVTerm top menu based on Windows 8 Tiles design provides host connection(s), help and settings tiles
• New web.config setting (AutoStart) which determines if user is auto-connected to last selected host or if the top menu is presented instead
• New Function Pin option will pin/display virtual function keyboard in selected locations, horizontal or vertical layout with different options for touch devices that can have a landscape or portrait viewport
• New Fonts available for OS/X and iOS devices
• For Extended Logging and Macro UserID management, Windows Security mode is supported and will use the logged-on Windows Userid for extended logfile names and Macro Authoring and private Macros folder name
• FVTerm will now use HTML5 Local Storage (when available) instead of cookies for user preferences–on first use, any cookies will be saved to local storage and deleted as cookies
• Further expanded browser compatibility (adding Opera) with HTML5 features used whenever available
• Host entry fields that specify numeric values only are now presented as type=”number” input types when using web fields and when this html5 feature is available in the browser–most notable when using iPads and other touch devices
• FVTerm Application is now a .NET 4.0 ASP.NET application.  FVTerm with Flynet 2013 is not compatible with SharePoint IIS sites and must reside in its own site (on the same server). This modifies deploy instructions and requires care in deploying the SharePoint UI and WP applications along with FVTerm.
• Added documentation for the FVTermParent javascript support which simplifies integration of an FVTerm iFrame in a hosting web application
• New web.config setting (IEActiveX) defaults that for Internet Explorer 7 and above the ActiveX Keyboard control will no longer be used, as almost all relevant emulation keys can be managed with javascript across all browsers including IE
• When the ActiveX control is configured for a version of IE, a new installation set of pages is provided to ensure clean installation without interfering with the first use of the emulator
• Added documentation for the FVTerm extended logger and additional examples including how to perform an automatic logon
• The FVTerm Application setup now includes prerequisites and supporting files for the SignalR technology which will be phased-in during 2013 as the backing technology connecting FVTerm clients with the application.  This will replace the current custom Ajax approach for managing event propagation back to the web client for unsolicited host writes and other server-side events.

TaskBar Tray Icon

• Service Restart will now optionally Recycle FV* IIS Application Pools instead of optionally restarting IIS
• If Flynet Studio is installed a launch item is now offered

Visual Studio Add-In

• Added support for Visual Studio 2012
• Improved some handling of ASMX and ASMX.cs files in web service projects
• Added support for .svc and .svc.cs files (WCF modules)

ViewerLib.dll and ViewerLib4.dll Assemblies

• HostScreenField new property-contents; lets developer read and write active screen contents using a HostScreenField object
• HostScreenField– length is now settable by code
• HostScreenField utilizes the write adjust property in the definitions file
• HostScreenField.value property when setting–did not properly truncate and pad based on active field length
• HostScreen added getField method which returns a HostScreenField using name based on the active default FieldMap
• HostScreen added getField returning a HostScreenField based on row, column and length
• HostScreen added setText using a field name based on the active default FieldMap and a value
• HostScreen added a get property, “name” which returns the same value as the getScreenName method
• HostConnection added a static method SetSessionUser to set the active user identifier (seen in the console as “LUOwner”) – parameters are (sessionkey, username)
• HostConnection added a method “identfyScreen(timeout)” which combines the functionality of HostScreen.waitForScreen(“*”) and HostConnection.getScreen()
• HostConnection session Pool methods fixed exceptions occurring when Flynet service isn’t running or is unavailable
• HostConnection.isBusy had incorrect interpretation of one of the internal wait flags
• HostScreen.waitForUpdate for VT applications was not always registering single-character echo changes
• HostScreen.putCommand – tighter compatibility with keyboard locking and isBusy, most noticable in VT terminal emulation environments
• HostScreen.oiaClock and HostScreen.oiainhibit better coordinated with putCommand

Flynet Viewer Studio (Build: 5.0.0.28)

Flynet Studio IDE

• Many UI Glitches and layout problems fixed for “magnified” screens (alternate DPI) common with many high-resolution laptops (125% was particularly problematic)
• When pinned to Taskbar, recent solutions opened will be available on right-clicking
• User navigation overrides reliability improved
• New option to set field names (checkbox: “Add length to Field Name when needed”) to have an appendix with the length when two fields with the same name have different lengths instead of qualifying with the fully qualified map name in generated code
• New option to set default for UI projects checkbox: “UI Projects use Separate Control Classes”
• Recording Import helper finds more mis-matches during the Pop-up and Mismatch finding stage
• Recording Import Helper now has a checkbox when a mis-match is found to replace the newly found screen reference as the active reference for the screen. This is very useful as the first screen encountered in many applications is not as “filled-in” as the next instance of the screen, so being able to choose which version of the screen to make the reference image saves having to do this as a separate step using the Screen property on the ScreenDef object.

Web Service and UI Generation

• Code generation options added Visual Studio 2012 and .NET Framework 4.5
• Code generation options now add a Web Site drop-down to pick which web site to add the application to (defaulted to “Default Website”)
• Code generation options now add an ApplicationPool setting to allow choosing a pool–defaults to the FVTerm v4.0 pool or a .NET FW 2 if the project is being generated as 2.0 asp.net
• Code generation with Framework 4.0 and Code Signing was not finding the sn.exe file used to generate SNK unique signing certificates
• Some navigation fixes for various permutations of screens and keys
• ViewerLib and ViewerLibPool references were specifying folder locations that were causing build errors-changed to no folder so GAC used

Web Service Generation

• Now supports generating Windows Communication Foundation (WCF) modules, which when chosen for a particular TaskModule, generate a .svc instead of the asp.net .asmx
• TaskMod.WebMethodsType – new property, ASP.NET SOAP or WCF MULTIPLEWCF Multiple adds generation of additional HTML and js files to support testing web services using jQuery and JSON, including integration of the testing parameters and results. Sample code for each task can be displayed for user incorporation into existing web applications
• WCF Multiple requires generation specifying .net framework 4.0 or higher
• Task.WcfRequestType property if WCF module – HTTP GET or HTTP POST for generated call type for JSON or REST-XML
• New Task Module wizard–added page to select SOAP or WCF Multiple as the generation type for the module–note, can mix ASMX and WCF if you want to

Enhanced UI Solution Generation

• Code generation for UI had the wrong default terminal emulation url–fixed to http://localhost/FVTerm/SCTerm.html
• Code generation added support for navigation through a dynamic menu, where the numbers of menu items change depending on user’s access profile, this includes a new NavigationType of DynamicMenu and a new property MenuOptionsRegex which enables location of menu options and text
• Added RPC.aspx.cs for sample of simple Ajax-JSON calls from client to enable better options for integration with javascript/jQuery
• Various bug fixes, tweaks and enhancements in generated code for SharePoint and other environments