New features in EPC 826 version of the Framework

Open and save your Framework web applications before executing them to create new .HTM and .JS files!

You can now create Framework-AJAX Applications to achieve optimal web performance with functionality close to that of a Windows rich client application.

See also Enable Framework for AJAX style applications.

In Windows applications the main Framework panes can be shrunk and expanded to allow more efficient use of screen real estate. Use the Allow Panes to be Shrunk and Expanded option to enable this functionality.

You can use the new Focused Input Field Style property to highlight the input field that has focus with a different style in Framework web applications.

The Demonstration Application has been significantly revised and updated.

To use it you need to open the new version of the shipped Framework definition in file VF_Sy001_System_LastShipped.XML.

You need to remove the old demonstration application from any existing Framework versions as it may no longer function correctly.

In web applications it is now possible to replace the Framework’s security model by specifying your own avCheckAuth method  (this has always been an option in Windows applications).

To do this you need to supply a LANSA function and enroll it into the Framework. Refer to shipped example function UFU0016 in process UF_SYSBR for more details. Also see IIP – Function to return web user authorities.

You can now specify the mini-filter as a panel to control all its display attributes. See AvMiniFilterPanel.

For example you can add combo boxes, drop downs, check boxes, and do instant editing on the panel.

It is now possible to use the Administrator interface in a deployed Framework web application to create users and groups, set authorities and custom property values.

This means that the Windows administrator components that were previously required in web deployment packages can now be omitted. See Creating Web Interface for Maintaining Users and Authorities.

Commands (and command tabs) can now be conditionally disabled or hidden depending on business object SubTypes.  

Also, you can use the Enable Child when Parent Selected and Enable Parent when Child Selected properties to control command availability.

An option has been added to instance commands to allow a command never to be the default, even when the user used it on a previous instance (see Default Command).

Commands can now be executed without any user interface at all, that is, hidden from the user. See Execute as Hidden Command and Hidden Command Handler Anatomy.

Instance Lists with Different Types of Objects are now also available in Framework web applications.

Peer business objects are now shown with their icon to make it easier to distinguish different types of objects.

You can Work with Hidden Child Objects by double-clicking an instance list entry.

Instance lists now have a toolbar. You can set the Instance List Tool Bar Location and the Instance List Tool Bar Height or Width in the Instance List/Relations tab of the business object.

ActiveX instance lists are no longer supported.

In Windows applications, Instance lists that are saved and restored between VLF sessions now include the user object name/type of any current super-server connection in the saved file names. This means that different versions of a saved instance list can co-exist for example  for Server1, Server2 and a Local DBMS.  

More details about the usage of command definitions are available on the Command Usage Tab:

• Default Command

• Hidden

• RAMP Destination

The Framework web application trace facility (+Trace=Y on URL) now displays the details of HTML pages arriving at the browser.

If an application detects a bad response from the web server, the user is given an option to analyze the nature of the error and display the problem HTML page. All details can be printed or copied to clipboard making it easier for end-users to provide helpful error information.

This version of the guide includes detailed information about Assessing Performance in Framework Web Applications.

The Position menu option can now be turned off by designers so that users will not be able to change the relative position of any of the Framework display panes.

You can specify an HTML page as the startup page for the Framework or an individual application. You can provide links to other resources from this page. See The Demonstration Application for an example.