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:
When Natural Security is active, it is now possible to define different development modes (either shared mode or private mode) for the individual libraries that are contained in a project. See the description of the Steplibs property page in Changing the Library Properties which is part of Using NaturalONE.
The Handling of missing objects option is now also used by the map editor and for debugging. Therefore, this option has been moved from the Source Editor preference page to the Projects tab of the Natural preference page. See Natural > Project in Setting the Preferences which is part of Using NaturalONE.
It is now possible to work with DDMs that have been linked to specific libraries using Natural Security. The linked DDMs are protected, and only authorized users are able to access them. For further information, see the following sections in Using NaturalONE:
Working with DDMs in the section Working with Natural Objects in Natural Server Mode.
The description of the Handling of missing objects option in the section Natural > Project in Setting the Preferences.
A new view, the NATdoc view, is now available. It shows how the NATdoc-specific comments in the source code will appear in the API documentation. For further information, see Previewing the API Documentation in the NATdoc View in Using NaturalONE.
A new type of console, the Natural command console for mainframes, can now be opened in the Console view. It allows you to enter Natural system commands directly in the Console view. For further information, see Using the Natural Command Console for Mainframes in Using NaturalONE.
It is now possible to search for code snippets in the Natural community, directly from Eclipse, and to include them in the source code using cut-and-paste. For further information, see Using Code Snippets from the Natural Community in Using NaturalONE.
In addition to scalar fields, array fields can now also be cloned within a map by dragging and dropping them with the CTRL key held down. For further information, see Adding Controls to the Map in Using NaturalONE.
To select the whole array prior to dragging it, either select the array field in the Outline view or click on one of the array elements with the ALT key held down, as described in Selecting Controls in the Map. Therefore, an array can be conveniently cloned by holding down both the CTRL and ALT keys while clicking on and dragging one of its elements.
The Natural-specific preference pages and the property pages for projects and libraries have been redesigned. Now, they have identical structures. In order to group the options in a more logical way, new pages and tabs are now available which contain options that were previously located on other pages. See the following sections in Using NaturalONE:
The Natural profile parameter ULANG can now be
set in the Natural preferences, in the project properties and in the library
properties. See the following sections in Using
NaturalONE:
Regional Settings > Options in Setting the Preferences
Regional Settings > Options in Changing the Project Properties
Regional Settings > Options in Changing the Library Properties
In the Natural Server view, it is now possible to display the contents of an object in read-only mode. For further information, see Listing Objects in Using NaturalONE.
In the Natural preferences, you can now specify that a message box is to be shown when a compile error occurs during the execution of an , or command. See Natural > Builder in the section Setting the Preferences which is part of Using NaturalONE.
In the Natural preferences, you can now specify that information about the download process is to be shown in the Console view each time you download objects from the Natural Server view into a new or existing project. See Runtime Execution > Server View in the section Setting the Preferences which is part of Using NaturalONE.
The following information applies when you create new projects using the option Group new objects by object type (either by using the wizard or by downloading an existing library or object from a Natural server into a new project).
The name of the group folder for DDMs has been changed from Data Definition Modules to DDMs. After an upgrade to NaturalONE Version 8.2.2, all new DDMs will therefore be added to a group folder named DDMs.
When you have created projects with previous versions of NaturalONE where you have used the above mentioned option, the DDMs are still stored in a group folder named Data Definition Modules. It is required that you make manual changes to these projects: you have to rename the Data Definition Modules folder to DDMs. It is recommended that you do this before you add or download additional DDMs.
On the first page of the deployment wizard for Natural applications, new options are available for the incremental deployment mode. For example, you can now determine that only the changed files are to be processed. See Deploying Natural Applications in Using NaturalONE.
New documentation is available which explains how to use the travel approval sample application that is delivered with NaturalONE. See Travel Approval Sample Application in Using NaturalONE.
This section describes new features and enhancements in Natural for Ajax and Ajax Developer. It covers the following topics:
New Property for BUTTON, NJX:BUTTONITEMLISTFIX and NJX:BUTTONITEM Controls
Changed Natural Code Generation for COLDYNAVIS and ROWDYNAVIS Controls
Natural for Ajax contains Application Designer Version 8.2.
You can now create your own workplace applications, with your own workplace resources. See Creating Your Own Workplace Application in Natural for Ajax.
A function tree in a workplace can have a depth greater than 3. Deeply nested tree nodes can be defined statically (MFWPBOOTSTRAPINFO) and dynamically (NJX:XCIWPINFO2 and NJX:XCIWPFUNCTIONS).
Using the new NJX:TRIGGEREVENT control, is now possible to trigger a user-defined event in the application.
The following controls, which were previously only available with Application Designer, can now be used with Natural for Ajax:
The new XCICONTEXT control supports sharing of simple data values between different pages in a session.
Support for the njx:natname property has
been added to the following controls:
The NATPAGE control now
supports the new property focusmgtprop. See also
Focus
Management in the section Some Common Rules for
all Controls in Natural for Ajax.
The BUTTON,
NJX:BUTTONITEMLISTFIX and
NJX:BUTTONITEM controls
now support the new property focusedprop.
The FIELD control now
supports the new property lengthprop.
The STATUSBAR control
now supports the new property straighttext.
For the COLDYNAVIS and
ROWDYNAVIS controls, the type of the generated data field in the
Natural adapter has changed. The valueprop
property is now generated as type Logical.
With previous versions, it was only possible to control the focus or to
modify the status of a control in the PROCESS PAGE UPDATE
statement when using the FULL option.
The following control properties are now updated in a PROCESS
PAGE UPDATE statement without using the FULL option:
statusprop,
displayprop and
invisibleprop. This new functionality requires
Natural Version 6.3.10 for Windows and UNIX or Natural Version 8.2 for
mainframes.
A new chapter is available which explains how to create PDF documents for Natural page layouts. See Working with PDF Documents in Natural for Ajax.
A new part is available containing descriptions of the TITLEBAR, HEADER, PAGEBODY and STATUSBAR controls. See Typical Page Layout in Natural for Ajax. The description of the NATPAGE control has been moved to this new part.
With NaturalONE Version 8.2.2, test functionality based on private-mode libraries is not supported.
