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:
The Natural Server view is no longer restored during the start of the Software AG Designer. It is now restored after the Designer has been started. See also Restore of the Natural Server View in Using NaturalONE.
The behavior of the Natural builder has changed in such a way that all changes within the current project are now automatically detected by the builder. It is no longer required that the Eclipse-specific Build Automatically command is enabled for this purpose. See also Understanding the Behavior of the Natural Builder in Using NaturalONE.
The information that is provided on the different property pages of the project properties has been rearranged. For example, all parser options are now available on the Parser page. In addition, the top-level page of the project properties now informs you whether the Natural project has been added from a protected or unprotected Natural environment. See Changing the Project Properties in Using NaturalONE.
When Natural Security is active, a Security node is now shown in the library properties. This node also includes the Steplibs page which was already available with previous versions. As of this version, it is also possible to define parser and runtime settings for a library which is protected by Natural Security. These settings override the corresponding Natural profile parameters in the project properties. See Changing the Library Properties in Using NaturalONE.
A background color is now shown for protected lines. The Natural source header consists of protected lines, and most lines in a source that has been generated by Construct or by the Code Generation component of NaturalONE are protected lines. See also the following sections in the Using the Natural Editors part of Using NaturalONE:
The background color for the protected lines can be changed in the Natural preferences. See Syntax Coloring in the section Setting the Preferences which is part of Using NaturalONE.
In the Natural preferences, you can now specify that all occurrences of a selected variable are to be marked in the source editor. This is enabled by default. See Mark Occurrences in the section Setting the Preferences which is part of Using NaturalONE.
In the Natural preferences, you can now specify whether the time stamp in the Natural environment is to be checked when a source is uploaded from the workspace to the Natural environment. You can also specify that a dialog is to appear in case of a time stamp conflict in which you can decide whether to proceed with the upload or not. See Natural > Builder in the section Setting the Preferences which is part of Using NaturalONE.
Before updating the Natural environment, it is now possible to compare the time stamps of the sources in the workspace with the time stamps of the sources in the Natural environment. All time stamp conflicts are collected in the new Time Stamp Conflicts view.
It is also possible to write the time stamp conflicts of a project to a log file or, if no conflict occurs, to update all objects of the project using command line arguments.
For detailed information, see Checking the Time Stamps in the Natural Environment in Using NaturalONE.
In the Natural preferences, you can now specify that status information about success or failure is to be shown in the Console view each time you check, stow or catalog an object in the Natural Server view. See Runtime Execution > Server View in the section Setting the Preferences which is part of Using NaturalONE.
If a source cannot be found in the workspace, a dialog box appears now asking whether you want to download the object from the Natural environment. See also Debugging Natural Applications in Using NaturalONE.
A new view is available in the Debug perspective which shows the current contents of the Natural stack. See Natural Stack View in the section Debugging Natural Applications which is part of Using NaturalONE.
When Natural Studio is installed on the same machine as NaturalONE, you can invoke Natural Studio from the Natural Server view and then edit the dialog directly in Natural Studio, using the dialog editor. In order to use this functionality, special prerequisites apply. For detailed information, see Working with Dialogs in Using NaturalONE.
This section describes new features and enhancements in Natural for Ajax and Ajax Developer. It covers the following topics:
Edit masks can now be specified for additional data types. In addition to the edit masks for numeric fields, which were supported with previous versions, edit masks are now also supported for alphanumeric, date, time, and logical fields. See Usage of Edit Masks in Natural for Ajax.
For compatibility reasons, the functionality from previous versions is still supported. For a description of the previous functionality, see Usage of Edit Masks in the appropriate version of the NaturalONE documentation. You can find this in Empower, Software AG's global extranet, at https://empower.softwareag.com/.
A new chapter is available providing some hints for multi language management in workplace applications which contain Natural layout pages. See Multi Language Management in Workplace Applications in Natural for Ajax.
Using the new NJX:OBJECTS control, it is now possible make assets that are contained in Natural binary variables (BLOBs) available to controls on the web page.
Using the new NJX:DOCUMENTLINK control, it is possible to embed hyperlinks into layouts which open a document in a pop-up dialog. This is also supported for documents contained in Natural binary variables which are provided by the NJX:OBJECT control.
Using the new NJX:NJXFILEUPLOAD2 control, it is possible to upload files from the client to the Natural server.
Using the new NJX:NJXFILEDOWNLOAD control, it is possible to add a link to your page layout for downloading files from the Natural server to the client.
It is now possible to upload dynamically generated PDF documents to the
Natural server. You can do this in two different ways: either with the new
build-in event
value-of-reportprop.onUploadPDF
of the REPORT control, or without
using the REPORT control as shown in the PDF_FOP_DEMO example in
the njxdemos project.
For environments where Natural for Ajax does not support the deployment with a .war file (currently, these are JBoss Application Server and Sun Java System Application Server environments), it is now possible to export the selected components to a specified folder. A corresponding option is now available in the deployment wizard. When this new option is selected, the deployment wizard creates plain folders and files which you can then copy into an existing server environment. See Deploying the Application in Natural for Ajax.
As of this version, the installation of NaturalONE is no longer described in the Software AG Installation Guide. It is now described within the NaturalONE documentation; see the new Installation documentation.
This new Installation documentation also contains the information which was previously available under the heading Before You Start, and also the System Requirements which where previously part of the Release Notes.
