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:
Importing Data Fields from the Layout Page of the Map Editor
Message Box for Confirming the Server Processing of Selected Objects
For mainframe environments in the Natural Server
view and also for UNIX, OpenVMS and Windows environments where the DDMs are
stored in the system file FDDM
, it is now possible to display all
accessible DDMs, including protected DDMs, in the library node. The new option
Display DDMs in Library is available for this purpose. See
Runtime
Execution > Server View in the section Setting
the Preferences which is part of Using
NaturalONE.
When you specify the new private_name
variable in the Natural preferences, the name of the associated private-mode
library is shown in the label decoration of a library node. See
Label
Decorations in the section Setting the
Preferences which is part of Using NaturalONE.
It is now possible to set so-called "development mode options" in Natural Security. These options determine how Natural Security controls the use of Natural server actions triggered by Navigator view actions. For detailed information, see Protecting the Natural Development Environment in Eclipse in the Natural Security documentation, which is part of the Natural documentation.
The prerequisite for this new feature is that a specific Natural Security version is installed in the Natural environment. For mainframe servers, this is Natural Security Version 4.2.7 cumulative fix 4 or Natural Security Version 8.2.2. For UNIX and Windows servers, this is Natural Security Version 6.3.11. These versions will be released later in this year.
Additional templates are now available for inserting recurring coding patterns into your source code. See Source Editor > Templates in the section Setting the Preferences which is part of Using NaturalONE.
Using the new Going to a Specific Natural Line Number in Using NaturalONE.
command you can now jump to a line in your source code which corresponds to the four-digit Natural line number which is used on a Natural server. The Natural line number is not the same as the Eclipse line number. SeeIt is now possible to protect one or more lines in your source code by using read-only tags. See Protecting Source Code Lines in Using NaturalONE.
The Show print margin option in the text editor preferences of Eclipse (Preferences > General > Editors > Text Editors) is no longer used to determine the column width when using the command. Instead, the new Maximum line length option is now available in the Natural preferences. See Struct in the section Setting the Preferences which is part of Using NaturalONE.
It is now possible to import data fields directly from the Layout page of the map editor. See Adding Controls to the Map in Using NaturalONE.
In the Natural preferences, you can now specify that a message box is to be shown when you are about to update the server environment using the Natural > Builder in the section Setting the Preferences which is part of Using NaturalONE.
or command. SeeYou can now instruct the debugger to skip code and to resume execution of the object with the source code line in which you have placed the cursor. The skipped code is not executed. See Going to the Next Statement in Using NaturalONE.
When the option Check time stamp conflicts is enabled in the Natural preferences, the time stamps are now also checked while debugging. When a source in the local workspace has a time stamp which differs from the time stamp of the corresponding source on the server, a dialog box appears, asking whether you want to update the source in the workspace with the source from the server. See also Starting the Debugger in Using NaturalONE.
NATdoc now searches each regular comment line which starts with
/*
and checks whether it contains a documentation comment
(/**
). This allows you, for example, to use different comments for
IDL generation and for NATdoc. See
Documentation
Comments in the Source Code in Using
NaturalONE.
NATstyle is a new development tool for NaturalONE. It helps you write Natural code which adheres to your coding standards. See Checking Natural Code with NATstyle in Using NaturalONE.
Important:
With NaturalONE Version 8.2.3, NATstyle is 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.
The new option Enable fail-on-error for Ant
scripts is now available on the first page of the deployment wizards
for Natural applications and Java applications. The setting of this option
determines in which cases a build failure will be triggered. In addition, new
command line options are available: -Dnatural.ant.failonerror
for
deploying Natural applications and -Dnatural.ant.java.failonerror
for deploying Java applications. See
Deploying
Applications in Using NaturalONE.
This section describes new features and enhancements in Natural for Ajax and Ajax Developer. It covers the following topics:
The new NJX:MASHZONE control allows you to integrate an ARIS MashZone application into a Natural for Ajax page.
The new option Enable fail-on-error for Ant
scripts is now available on the first page of the deployment wizard
for web applications. The setting of this option determines in which cases a
build failure will be triggered. In addition, the new command line option
-Dnatural.ant.ajax.failonerror
is available. See
Deploying the
Application in Natural for Ajax.
With NaturalONE Version 8.2.3, test functionality based on private-mode libraries is only supported with an RPC server which runs on a mainframe.
The command Test Software AG IDL, which is available when EntireX is installed, is not supported for private-mode libraries.
NaturalONE Version 8.2.3 is the last version running with Oracle Java Version 1.5. As of NaturalONE Version 8.2.4, Oracle Java Version 1.6 will be used.
Note:
Oracle Java Version 1.6 is currently already required for installing
NaturalONE with the Software AG Installer.
NaturalONE Version 8.2.3 is the last version which supports Internet Explorer 6.0. For a list of the currently supported web browsers, see Supported Browsers in the Installation documentation.