This document covers the following topics:
This section describes new features and enhancements in NaturalONE's basic functionality for Natural application development. It covers the following topics:
It is now possible to create a new library and a new library folder at the same time. For this purpose, the new option Use folder as library folder is available in the dialog box which appears when you create a new library. See Creating Libraries in Using NaturalONE.
This new option is also available in the dialog box which appears when you create a new Natural object. See Creating Natural Objects in Using NaturalONE.
The steplib handling for Natural environments which are protected by Natural Security has been improved. An additional button is now available on the Steplibs property page of the library properties. Using this button, you make sure that the steplib definitions in your local workspace are identical with those in the associated Natural environment. In addition, the dialog box which appears when the steplib definitions do not match (for example, when you update a project) has also been improved. Using the buttons in this dialog box, you can now either update the local steplib definitions automatically and continue with the update, or you can cancel the update. See Steplibs in the Changing the Library Properties which is part of Using NaturalONE.
In addition to downloading missing objects using the Dependencies view, it is now possible to download missing objects using the source editor. See Opening Referenced Objects and Jumping to Variable Declarations in Using NaturalONE.
In the Natural preferences, you can now specify that a dialog box is to be shown when you are about to cancel a build. See Natural > Builder in the section Setting the Preferences which is part of Using NaturalONE.
The Regional Settings page of the Natural preferences now provides the additional RTL Languages tab. Using this new tab, you can define options for Arabic shaping. See Regional Settings > RTL Languages in the section Setting the Preferences which is part of Using NaturalONE.
Using NaturalONE contains a new section which explains how Arabic shaping is supported by NaturalONE. See Arabic Shaping.
Important:
With NaturalONE Version 8.2.4, support for Arabic shaping is
provided as a preview version. There will be no support for this preview
version. Any feedback from our customers on this new feature is greatly
appreciated. Since support for Arabic shaping is still under development, a
later version of NaturalONE may include substantial changes to this type of
support.
If a Natural Development Server (NDV) on the mainframe is started with
the configuration parameter UNICODE_SOURCE=NO, no error was
displayed with previous versions of NaturalONE when a source was uploaded to
the server in which the user has entered a character which is not contained in
the source's code page. Instead of displaying a conversion error, the
unmappable character was replaced with a substitution character. As of this
NaturalONE version, an exception will be thrown in the above situation and the
source will not be uploaded to the server.
In the Natural preferences, the Visual mode option has been moved from the Project tab of the Natural page to the new RTL Languages tab of the Regional Settings page. It has been renamed to Visual order. See Regional Settings > RTL Languages in the section Setting the Preferences which is part of Using NaturalONE.
The NaturalONE parser is now able to recognize, parse and highlight the Natural SQL statements for DB2 for z/OS Version 9 in the source editor. These statements apply to the mainframe only. The prerequisite for this new functionality is that your project is associated with a mainframe environment (for example, via the Map Environment dialog box). Please note that only the runtime on a mainframe server is able to execute these statements.
With NaturalONE Version 8.2.4, NATstyle is still provided as a preview version. There will be no support for this preview version. Any feedback from our customers on this new development tool is greatly appreciated. Since NATstyle is still under development, a later version of NaturalONE may include substantial changes to NATstyle. These changes may result in incompatibilities, for example, when checking the Natural code with user-created NATstyle configuration files.
See Checking Natural Code with NATstyle in Using NaturalONE.
This section describes new features and enhancements in Natural for Ajax and Ajax Developer. It covers the following topics:
nat:browser.end is a new built-in event. This is event is
raised whenever the session is terminated by a browser action:
Closing of the browser.
Navigation to another page in the browser.
Programmatic close in a workplace (for example, close all session functions).
In addition, this event is raised in the following cases:
Timeout of the session.
Removal of the session with the monitoring tool.
After the event is raised, the Natural session terminates.
See Built-in Events and User-defined Events in Natural for Ajax.
The Layout Painter now supports copy-and-paste operations between different page layouts.
NaturalONE is now delivered with a new optional component: the Lifecycle Manager. The Lifecycle Manager is used to deploy Natural applications and Natural for Ajax applications (or specific versions thereof) to different environments and to keep track of the installed applications in each environment. It is based on CentraSite and uses Natural projects. For detailed information, see the Lifecycle Manager documentation.
The Lifecycle Manager is installed together with NaturalONE. In the Software AG Installer wizard, it is shown when you expand Designer > NaturalONE. When you install it, several files are copied to your NaturalONE installation. For information on how to proceed after that, see System Requirements and Installation and Configuration in the Lifecycle Manager documentation.
Workplace applications that have been developed using Ajax Developer are not yet supported by NaturalONE's basic functionality for application development.
