This document covers the following topics:
The new option DATA is now available for the
PROCESS PAGE UPDATE statement. This
option behaves like the FULL option, with the exception that the
MODIFIED status of the control variables is not reset.
In the properties of the Natural Runtime startup service, the option Allow the service to interact with desktop is now enabled by default. As a consequence of this change, errors and messages generated by runtime processes that are started under the control of the startup service are now displayed on the user's desktop or on the console desktop of the Windows terminal server.
The Natural Web I/O Interface is now delivered in the Version 1.3.8.
Using the new session option Check for numeric input, you can now decide whether numeric input fields are to be validated or not. See Overview of Session Options in Configuring the Client which is part of the Natural Web I/O Interface documentation.
It is now possible to set the cursor (caret) to output fields. The
Natural system variables *CURS-LINE,
*CURS-COL and *CURSOR
are now set correctly when placed on an output field. It is no longer required
to enable caret browsing in the web browser.
With the XSLT files that are used for the conversion of the Natural Web
I/O Interface screens from the internal XML format to HTML, the output fields
are now generated as HTML read-only <input>
elements instead of <span> elements.
It is now possible to use your own XSLT files with Internet Explorer and Firefox (Java EE-based servers only). These files must have special names. See XSLT Files in Configuring the Client which is part of the Natural Web I/O Interface documentation.
The Natural for Ajax documentation has been removed from this Natural documentation. The most up-to-date Natural for Ajax documentation is always available at http://documentation.softwareag.com/.
The Natural Web I/O Interface documentation has been changed in such a way that it now only contains the configuration information for the Natural Web I/O Interface client. All information concerning the client configuration for Natural for Ajax is now available in the above mentioned Natural for Ajax documentation.
