OpenSpan Version 5.1 Release Notes

Date: July 31, 2011

Overview... 1

Global Changes. 2

New Features. 2

OpenSpan Runtime. 2

OpenSpan Studio.. 3

Features from earlier releases no longer included in OpenSpan Studio version 5.1. 3

OpenSpan Server. 4

Installation. 4

Configuring OpenSpan Server 4

Deployment packages. 4

Customize package features. 4

Package Management and Promotion. 5

Reporting. 5

Comparing and Contrasting OpenSpan 5.1 with and without OpenSpan Server. 6

Obtaining OpenSpan Software. 6

Installation Instructions and System Requirements. 6

Known Issues and Limitations. 6

Resolved Issues since OpenSpan 4.5 Service Pack 1. 7

64-Bit Application Support Matrix. 12

Overview

These release notes contain important information that you should know before you install OpenSpan 5.1. Prior to installing this release, you should familiarize yourself with all of the resolved issues and new features listed in this document.

OpenSpan Version 5.1 introduces significant functional changes to OpenSpan Studio (Standalone/Plugin for Visual Studio 2008), Enterprise Runtime, and Events Runtime. The earlier separate OpenSpan Events Server does not exist with this release. Version 5.1 optionally includes a Web-based server that provides group and user control over OpenSpan Runtime deployments and insights into user desktop interactions across an enterprise for the purposes of process improvement and compliance.

OpenSpan Studio and Runtime 5.1 are compatible with 64-bit Windows operating systems. The list of supported applications and technologies as of the release date is located under the section titled 64-Bit Application Support Matrix on page 12 of this document.

Additionally, Version 5.1 addresses a number of issues and provides updates to previous OpenSpan releases. It provides a single high-quality update that minimizes deployment and testing complexity for our customers.

Global Changes

There are two important technology additions with OpenSpan 5.1: 64-bit compatibility and updates to the OpenSpan Driver.

· 64-bit compatibility. OpenSpan Studio, Runtime, and Server 5.1 run natively in 32- and 64-bit environments. A table at the end of this set of Release Notes lists current, tested OpenSpan 5.1 compatibilities with the superset of business software applications commonly targeted by customers for user process improvement.

· OpenSpan Driver. While this is a largely unseen change, it represents a significant advance in how OpenSpan leverages the host operating systems for execution. The driver (formerly openspan.sys, now openspan.x32.sys and openspan.x.64.sys) no longer watches for adapter processes and reports them to start injection; rather, it watches for every process creation and reports the information to a set of services. The payoff to the developer and desktop user is speed and overall Runtime efficiency.

New Features

This release includes new and updated features.

OpenSpan Runtime

In OpenSpan 5.1, Runtime packages can be deployed directly from OpenSpan Studio, as in previous releases. However, OpenSpan Server 5.1 can be used to manage Runtime packages based on configuration, user group identity, and iterative modifications to deployed Runtime package features. The main updates to Runtime 5.1 include:

· Runtime user package download from OpenSpan Server 5.1 based on group association. Users are defined using OpenSpan Server 5.1’s administrative tools as members of named groups. When an end user signs on to a desktop with Runtime 5.1 linked to OpenSpan Server 5.1, the authentication process loads a particular Runtime package that is tailored to that individual’s group assignment.

· Metadata download based on Runtime package user group assignment. Runtime 5.1 users working in conjunction with OpenSpan Server 5.1 can have Runtime packages assigned that include metadata related to task-specific processes. This is useful for a number of reasons, including interaction with the Process Toolbar described below. The metadata is tagged separately in the Events table of the OS_Server database and can be used for custom reports on application and user activity.

· Runtime can capture Application Usage Events data without a loaded project. Desktops with Runtime 5.1 installed can send High Level Events data related to application usage to the Events database table used by OpenSpan Server 5.1 for analysis without downloading a Runtime package. One resulting scenario is that application and user processes on desktops can first be monitored, analyzed, and then improved later with automations in Runtime packages.

· OpenSpan Server authentication dialog in the Runtime system tray menu. The Runtime 5.1 system tray now allows users to authenticate with OpenSpan Server 5.1 upon workstation sign-on to run the latest assigned Runtime packages. Different users can sign on to a single workstation and access their assigned Runtime packages using this new function.

· Process Toolbar. OpenSpan Runtime 5.1 users connected to OpenSpan Server 5.1 have the option of accessing a floating desktop Process Toolbar that works in conjunction with custom metadata to collect tailored Events information.

· New diagnostics interface to manage the native Trace facility. Error logging and diagnostics have significantly expanded inside Runtime 5.1 as well as within OpenSpan Studio 5.1.

OpenSpan Studio

OpenSpan Studio 5.1 can build and deploy standalone Runtime packages as in previous versions. But OpenSpan Studio 5.1 capabilities have been strengthened through direct communication with OpenSpan Server 5.1. OpenSpan Studio 5.1 includes these new features:

· Connectivity to OpenSpan Server – Direct package upload. OpenSpan Studio 5.1 uploads Runtime packages with any configuration directly to OpenSpan Server 5.1.

· ProcessPublisher Component. The ProcessPublisher, found in the toolbox, is similar to the Custom EventPublisher, and is used for reporting metadata (attributes, facts, dimensions) on processes executed on the user desktop.

· Changes to Events: EventPublisher, EventContext, EventFileWriter. Metadata is now stored locally in a project, rather than on the server, and removes the need for an Event metadata provider interface in OpenSpan Studio. Note: Earlier versions of Events components (4.5 SP1 and earlier) do not automatically convert or upgrade. There are other significant changes to Events projects. The Web Service and Queue Connectors are not used on version 5.1 because of direct communications with OpenSpan Server and because messaging is no longer supported. And finally, the SampleConnector has been relocated to a new assembly called EventFileWriter. Batching and compression are added, and reliable messaging removed.

· Diagnostics interface to manage native Trace facility. Error logging and diagnostics have significantly expanded inside OpenSpan Studio 5.1. A Trace API allows selection of several different options and sub-selections.

· Ability to run a solution for a selected User Group and promotion level from within OpenSpan Studio. Additions to the OpenSpan Studio 5.1 user interface correspond to package management features on OpenSpan Server to ensure consistent versioning.

· Ability to publish events from standalone adapters. This was implemented in OpenSpan 4.5 Service Pack 1, and is formally included in the 5.1 feature set. Adapters hosted using the .NET API can publish Events now as well as standard adapters from within OpenSpan Studio.

· Screen shots of interrogated controls, and screenshot upload to OpenSpan Server. Interrogated controls are now saved as a graphic file for quick reference, showing the interrogated application’s user interface with the control highlighted. These screen shots follow the OpenSpan Solution as it is uploaded to OpenSpan Server 5.1; when changes to Runtime packages are made using the Features functions on OpenSpan Server, the screen shots are available for reference and confirmation of the exact choice of controls.

Features from earlier releases no longer included in OpenSpan Studio version 5.1

This list is a recap of features in OpenSpan Studio 4.5 SP1 and earlier that have been removed to streamline communications and operations with OpenSpan Server 5.1.

· All messaging components have been removed.

· Since OpenSpan Events Server is no longer part of the architecture, Event Queue and Web Service connectors, formerly used to transport Events Server data, are no longer available or needed for transport. However, the EventPublisher and EventContext components are still available for sending data to OpenSpan Server, along with a new component, ProcessPublisher (for custom metadata). EventFileWriter takes the place of the earlier SampleConnector for writing data.

· Remote Configuration is no longer supported, but was replaced by OpenSpan Server 5.1’s deployment management functions.

OpenSpan Server

The OpenSpan 5.1 architecture places a completely new communications, management, and analysis product, OpenSpan Server, between OpenSpan Studio’s development processes and the Runtime packages deployed to user desktops. The following sections explain, at a high level, what OpenSpan Sever adds to the OpenSpan monitoring, automating, and process improvement chain. Some of the features described previously for OpenSpan Studio and Runtime that relate directly to OpenSpan Server-based architecture are also recapped below.

Installation

If you’re familiar with OpenSpan 4.5 or earlier, you’ll notice differences beginning with Server installation and configuration. Part of the installation process includes running batch files that create the OS_Server database. Open this database with SQL Server Studio and you’ll see that the Events tables, which used to populate the separate OS_Events database, are merged into the new, single structure.

Configuring OpenSpan Server

Initial configuration of OpenSpan Server 5.1 includes establishing the directory of authorized users. Currently there are two categories – server users, who have privileges across server functions, and Runtime users, who are limited to logon from the Runtime desktop.

Users are can entered manually, or imported from Active Directory. Users are then assigned to Groups (or the Groups can be used intact if previously set up and imported from Active Directory).

Deployment packages

Runtime deployment packages can be created in OpenSpan Studio 5.1 and directly uploaded to OpenSpan Server 5.1, where they are assigned to Groups. Let’s say that end user Ralph is assigned to the Agents Group via OpenSpan Server 5.1, and signs on to his workstation that is configured with OpenSpan Runtime 5.1. He then authenticates with OpenSpan Server from the Runtime desktop menu, and is authorized to run a package with a specific configuration, version, and feature set assigned to his group. Later, if end user Sally, who is assigned to a different group, logs on to the same (or a different) workstation, OpenSpan Server could assign her a Runtime package with a completely different feature set.

Customize package features

The previous section mentioned modified features in Runtime packages. Features in this context are overlays on the Runtime package which are changed through the OpenSpan Server user interface. Once a Runtime package is uploaded to OpenSpan Server 5.1, it can be modified in different ways that change its functions without redoing an automation earlier in the development process in OpenSpan Studio. Runtime package features that can be modified through OpenSpan Server are:

· Default Values. The Features interface in OpenSpan Server 5.1 allows appropriate controls in an OpenSpan Solution to be set when the solution is run. For example, a credit card account number field in a referenced CRM application can be set to blank out actual account numbers for security and compliance purposes. But since different features can be assigned to different Groups, developers can produce “standard” solutions which are then fine-tuned on the Server. Default values can be set for check boxes, radio buttons, combo boxes, and list boxes.

· Popup Help. OpenSpan Server 5.1 can add popup help to any interrogated control, and assign different versions of popup help to different Groups. This is useful when end-users might need different process guidance based on different roles using the same core desktop application.

Package Management and Promotion

Deployment packages uploaded to OpenSpan Server 5.1 stay in “sandbox” mode for changes and testing until formally promoted from Development to Production status. This ensures that Runtime users get the current Production version while Server users can continue to modify them separately.

Reporting

OpenSpan Server 5.1 replaces the earlier OpenSpan Events Server, and adds a native data visualization capability. Events data is sent from end-user desktops using OpenSpan Runtime 5.1 to the OS_Events table in the OS_Server database. There are several reporting categories:

· Adapter (“generic”) Events. These are events generated by OpenSpan adapters as configured on a given adapter to produce events in response to control events (such as a button click).

· Custom Events. These are events generated in projects using the EventPublisher component in automations in OpenSpan Studio.

· Application Usage Events. These are also known as “no-touch” events. Application Usage Events are generated by OpenSpan Runtime, reporting on application operations on the desktop, including application focus, process start/stop times, idle time, and other high-level application information.

· Process Events. These are events generated either in conjunction with the Process Toolbar (if enabled in OpenSpan Runtime), or in projects using the ProcessPublisher component in automations.

OpenSpan Server 5.1 provides an intuitive set of visualization tools.

· Application and Process Activity Reports. These provide insights into how long processes take to complete and how often they are started, finished, and abandoned. They give an accurate measure of application usage (duration) and metrics (keystrokes, errors, churn, copy/paste events, etc.).

· User Performance Reports. These reports measure user performance and provide statistics on which users are most and least efficient.

Comparing and Contrasting OpenSpan 5.1 with and without OpenSpan Server

Without OpenSpan Server, it’s possible to develop and deploy OpenSpan Runtime packages directly to user desktops, though the using organization must define:

· A scheme for package configuration management – versioning, feature mix, revisions and feedback

· A deployment mechanism – SMS, HTTP, direct installation, etc.

Under this concept – without OpenSpan Server – the using organization foregoes:

· Events collection and reporting for process monitoring

· Advanced Runtime package management – versioning, customization, User and Group control and access

· Other supporting productivity enhancements

Incorporating OpenSpan Server 5.1 into the architecture makes Runtime package versioning, feature modification, accountability, and user access and management easier, faster, and more secure. Data on user processes can be collected and analyzed quickly and accurately, and improvement solutions move from development and business analysts to the end-user desktops across an enterprise or geographically disparate locations with greater speed and effectiveness.

Obtaining OpenSpan Software

OpenSpan Studio 5. 1 Stand-alone Edition, OpenSpan Studio 5.1 Plug-in for Visual Studio 2008, and OpenSpan Runtime 5.1 are available using a customer login from the OpenSpan Support Portal.

Current OpenSpan customers who own a licensed server product (e.g., OpenSpan Events Server) can download OpenSpan Server 5.1 using their customer login from the OpenSpan Support Portal.

Installation Instructions and System Requirements

· OpenSpan Studio 5.1 Plug-in for Microsoft Visual Studio 2008 Installation Guide

· OpenSpan Studio 5.1 Stand-alone Edition Installation Guide

· OpenSpan Runtime 5.1 Installation Guide

· OpenSpan Server 5.1 Installation protocols are available to customers who obtain OpenSpan Server 5.1 from the OpenSpan Support Portal.

Known Issues and Limitations

OpenSpan’s 64-bit implementation is limited at present to the list in the section titled 64-Bit Application Support Matrix below.

Resolved Issues since OpenSpan 4.5 Service Pack 1

This table summarizes the significant changes and updates contained in OpenSpan Release 5.1, compiled since the release of OpenSpan 4.5 Service Pack 1.

Hotfix	Resolution
4.5.361.41	4.5 rebuild of CR 11293 with CR 9658
4.5.361.42	Client-specific fix for CCF and Siebel project that generated a .NET Framework exception. Retroactively updates the following earlier hotfixes in the 4.5.361 series: 12, 20, 23, 34, 38, 41
4.5.385	Restores ValueChanged and ValueChanging events for hidden objects on a Web page.
4.5.385.1	Ensures operation of Realiable Messaging under high volume for OpenSpan Events.
4.5.385.2	Ensures GetTableMethod returns the complete, requested dataset.
4.5.385.3	Internal/Test.
4.5.385.4	Exposes SelectedIndexChanged event for Siebel combo boxes.
4.5.385.5	Exposes the Href property to the automation surface for an Anchor tag.
4.5.385.6	Modifies project assembly code generation to ensure that WinForms have additional code injected, making them scale correctly at runtime.
4.5.385.7	Internal/Test.
4.5.385.8	Fixes an issue where sending function keys greater than F9 does not work in a DOS emulator. The input record structure now sets the Unicode character value correctly to zero for all function keys.
4.5.385.9	Corrects an issue with Object Explorer preventing the TableProvider property from getting set and populated correctly.
4.5.385.10	Internal/Test.
4.5.385.11	Promotes support for McAfee HIPS forward.
4.5.385.12	same as 4.5.385.120
4.5.385.13	Improves certain instances of Web page matching.
4.5.385.14	Fixes instances of Windows application not opening in reparented container.
4.5.385.15	Allows ability to capture page title and URL after PageLostFocus event arguments by adding a cached title and URL and the synchronous FormLosingFocus event.
4.5.385.18	Adds several translators for Myriad CRM.
4.5.385.21	Corrects some memory leaks from dynamic memory not being deallocated, lack of cleanup from unsubscription notifications, set window properties not removed. Updates 4.5.385 series hotfixes 14, 17, 18.
4.5.385.100	Events Server Install; cumulative hotfixes plus an update to allow the ability to capture Windows form title when FormLostFocus event fires.
4.5.385.101	Port of an OpenSpan 4.5 SP1 hotfix that corrects certain unanticipated Internet Explorer 8 crashes.
4.5.385.102	Ensures that the VerifyElement and PreviousSibling methods are exposed.
4.5.385.103	Ensures that automations support COM object methods and properties invocation.
4.5.385.104	Ensures TextChanged event for TEXTAREA tag fires.
4.5.385.105	Fixes issue with TextChanged event not firing for a specific AWT label (Java).
4.5.385.106	Corrects a Target Invocation Exception occuring when interrogating a specific Java Swing application.
4.5.385.107	Corrects SendKey combination errors occurring on a specific client DOS emulator.
4.5.385.108	Modifies the Event Service Web Service Connector to add the following new properties to control how Web proxies communicate with the Event Server: UseDefaultWebProxy, BypassProxyOnLocal, ProxyAddress.
4.5.385.109	Adds exception handling for some uses of Runtime via code in a Windows Service under Windows 7.
4.5.385.110	Corrects other SendKey combination errors occurring on a specific client DOS emulator.
4.5.385.111	New injection modification; ensures that McAfee HIPS hotfix to 4.5 SP1 is only enabled if requested via the OpenSpan.ini file.
4.5.385.112	Fixes Automation Designer crashes occurring when deleting a design block.
4.5.385.113	Part of reference 12065. Allows turning off Container events as generic events. ensures correct batching in the WebServiceConnector, and corrects truncation errors of columns on SQL Server bulk inserts.
4.5.385.114	Modifies Try-Catch logic to function correctly with automation entry points.
4.5.385.115	OpenSpan Events Server/WebServiceConnector fixes. Ensures correct batch duration and sending, functions in the Web service connector; fixes data column truncation, server connectivity; stops reporting of Container creation; ensures correct data transformation and reporting; deconflicts batching and Runtime.
4.5.385.116	Returns the ability formerly available in 4.1 to interrogate some Java applications.
4.5.385.117	Implements latest version of High Level Events.
4.5.385.118	Port of earlier Hotfix 10433 (4.1 SP1) to 4.5 SP1.
4.5.385.119	Adds PowerBuilder 12 support to 4.5 SP1.
4.5.385.120	Allows Siebel 7.8 popup window to be created when Siebel windows are hidden, whether individually or using the HideApplicationAtRuntime property.
4.5.385.121	New OpenSpan Events Server installer, new High Level Events Properties SQL statements.
4.5.385.122	Allows the .NET ContextMenuStrip to work on a Windows form at runtime.
4.5.385.123	Ports Hotfix 5461 (4.1 SP1) to 4.5.SP1.
4.5.385.124	Fixes issues with SalesForce component timing out. Also addresses malformed queries from the SalesForce connector.
4.5.385.125	Adds latest VirtualBroker features to 4.5 SP1. Consists of VirtualBroker Server installation and Hotfixes for OpenSpan Studio (plugin or isolated) and OpenSpan Runtime.
4.5.385.126	Corrects issues with controls being destroyed different numbers of times during runtime and interrogation.
4.5.385.127	Fixes internal exceptions that only produce one partial screen instance when attempting to retrieve all cloned instances via code. ClonedInstanceBroker no longer requires ProjectConfigurationService when used in code.
4.5.385.128	Added an ability to turn Runtime MRU (Most Recently Used) feature on and off via RuntimeConfig.xml "MRU" setting. MRU is set up to be enabled by default.
4.5.400.0	Corrects problems of watches being unavailable after a ListLoop.
4.5.500.1	When including an OpenSpan project in a .NET or other Visual Studio solution, ensures required assemblies are output to build a standalone application.
4.5.500.2	Provides translator support for grid (GXWND) in Clarify 7.5
4.5.500.3	Ports specific earlier Hotfixes to a customer Windows 7 environment.
4.5.500.4	Remote Config installer addresses communications issues with Runtime.
4.5.500.5	Corrects Salesforce component load errors.
4.5.500.6	Improves High Level Events performance with aggregation tables; adds new properties OPERATIONID, URLPATH, and URLQUERYSTRING. Improved idle detection and reporting.
4.5.500.7	VirtualBroker Installer.
4.5.500.8	Adds a Quota property to all ServiceClient connector bindings for when the connector fails to retrieve a large data set from the server with a message quota size error. Connects tables from a Web service tableset to TableViews so they can be queried within automations.
4.5.500.9	Allows updating of an individual field in the LookupTable. The new UpdateField() method has the following parameters. Key - Key of record to update. Column Name\Index - Name or index of column to update. New Value - New value of the field.
4.5.500.10	Hides Runtime window for High-Level Events; makes RuntimeForm transparent and set to start minimized.
4.5.500.11	Modifies OpenSpan.Scout.dll and Java translators for better performance with some particular Java applications and child processes.
4.5.500.13	Fixes exceptions occuring in a specific customer application set.
4.5.500.14	Improves data transformation for High Level Events when high volumes are being processed.
4.5.500.15	Corrects issues resulting around losing focus (and other) events with the Clarfy login form.
4.5.500.16	Stops unexpected exceptions when a user changes forms on an internal customer application.
4.5.500.17	Java matching issue. NativeControl.Initialize() was modified to ensure all enqueued windows are located to account for all window created processes.
4.5.500.18	Customer-specific fix that corrects match rule problems related to RichTextboxes in Clarify.
4.5.500.19	Corrects a second exception to Reference Number 13171, 4.5.500.16/18
4.5.500.20	The Events edition of OpenSpan Runtime periodically generated the error message “Error loading project. The OpenSpan Runtime prevented design component ‘OpenSpan.Adapters.Web.Controls.Textbox’ from being accessed because it would have violated the license for the installed edition. Please contact your assigned OpenSpan product support representative or your network administrator.” This hotfix corrects the problem by removing the property set checks for the TagName property.
4.5.500.21	Changes logic in WaitAll so that execution does not return to ParallelProcess until all work is completed.
4.5.500.22	Fixes a problem interrogating Siebel 8.0 and matching a Windows adapter by eliminating search by window position.
4.5.500.23	High Level Events was having issues with incorrect ExePath if a process ID was reused. This hotfix includes refactored ExePath catching logic to account for process ID reuse.
4.5.500.24	Updates to the OpenSpan.Native32.dll, OpenSpan.Translators.Java.dll

64-Bit Application Support Matrix

The OpenSpan 5.1 release supports the following 64-bit applications and technologies. Conversion is an ongoing process and this table will continue to grow. Contact OpenSpan Support for the latest summary.

Application or Technology	Versions or Details
Internet Explorer	IE6 x86, IE6 x64 IE7 x86, x64 IE8 x86, x64
Java	6 x86 6.0 x64 Java 1.4 x86 Java 5 WoW64 Java 5x86 Java 6 WoW64 Java 6 x86 Java 6 x64
Siebel	Siebel 7.7 Siebel 7.7 (Wow64) Siebel 7.8 Siebel 7.8 (WoW64) Siebel 8.0 Siebel 8.0 (Wow64)
.NET	1.1 x86 1.1 x64 2.0 x86 2.0 x64 2.0 (WoW64) 3.0 x86 3.0 x64 3.0 (WoW64) 3.5 x86 3.5 x64 3.5 SP1 x86 3.5 SP1 x64 3.5 (WoW64)
Powerbuilder	Powerbuilder 7.0 Powerbuilder 10.5
SAP	SAP 6.2 SAP 6.2 (WoW64) SAP 7.1 SAP 7.1 (WoW64) SAP 7.2 SAP 7.2 (WoW64)
Remedy	Remedy 7.0.1.11 Remedy 7.0.1.11 (WoW64) Remedy 7.1.0.7 Remedy 7.1.0.7 (WoW64) Remedy 7.5 Remedy 7.5 (WoW64)
HLLAPI Emulator	HLLAPI Extra, CAIL, Reflection, PComm, Rumba
Console Adapter	Works in all tested regions
MS Office	MS Office 2002 MS Office 2003 MS Office 2007
DevExpress	DevExpress 3.2.4 DevExpress 7.1.2 DevExpress 8.3.8
Control Regions	N/A
MS Common Controls	V.5 tree view, status bar
Active Listbar	N/A
Active Bar	N/A
Oracle Forms Client	Oracle Forms 6i (6.0.8)
Clarify	7.5.0.10 (WoW64) 12.0.0.0 (WoW64)

Note: Citrix has its own matrix, because of Citrix-imposed variations and anomalies between server and client versions. The following list has been verified for OpenSpan 5.1 compliance:

Server	Client	Command Line
Xenapp v6.0	Online Plugin v12.1	%**
Xenapp v6.0	Online Plugin v11.2	%**
Xenapp v5.0	Online Plugin v12.1	%**
Xenapp v5.0	Online Plugin v11.2	%**
Presentation Server v4.5	ICA Client v11.2	%*