Tags:
create new tag
view all tags

APPX 6.2.0 Features

This page provides an overview of the new features in APPX 6.2.x


Overview

This release is primarily focused on the repair of bugs, found in both the 5.5.x & 6.1.x versions of Appx, along with a few enhancements.

Noteworthy enhancements include updates to the JSON parser API, XML Writer APIs, the Appx Data API, APIs for encoding/decoding base64 data, the addition of the ability to enforce limited user licenses and the ability use the Html client to develop and debug APPX applications.

Changes in Release 6.2.0

Here is a list of the changes in Release 6.2.0:

JSON Parser APIs

You can use the following APIs to parse a JSON file or string:

--- .JSON PARSE
--- .JSON PARSE FILE

XML Writer APIs

You can use these new APIs to create a well formatted XML file.


.XML WRITER OPEN
--- .XML WRITER CLOSE
--- .XML WRITER ELEM START
--- .XML WRITER ELEM END
--- .XML WRITER ADD DATA
--- .XML WRITER CDAT START
--- .XML WRITER CDAT END
--- .XML WRITER ADD ATTR

Base64 Data Encoding/Decoding API

You can now encode up to 24k and decode up to 32k of Base64 data, The two new routines are: .CONVERT TO BASE64 and .CONVERT FROM BASE64

APPX Data Services API Enhancements

The data API now takes advantage of the new JSON PARSE subroutine. The new subroutine provides the incoming data as Unicode. As the side effect, the PATH field in JSON file cannot be a key anymore since its size is larger than Appx key size limit. As a work around you can use PARENT RID to read through the hierarchy or use PATH HASH which is the hash value of the PATH field.

Based on the selected ‘Mode’ setting for each data services command, the parsed JSON will be written to a different file. For example, if the ‘Mode=small’ the parsed JSON is written to the file 0LA RAWJSONS, if ‘Mode=medium’ the data will be written to 0LA RAWJSONM and, for ‘Mode=large’ the data will be written to the 0LA RAWJSONL file. You can check 0LA WEBSERVICES JSON MODE to find out where the parsed JSON records were written.

Note again that the incoming JSON data no longer has a limit. If the incoming data is more than 1M characters, APPX writes the data to a file, then parses the content of the file.

Limited Access User Rights

The requirements of the limited access user rights have been implemented in this release.

To review, starting in APPX version 5.0.3, the license agreement defined Limited Access User Rights as follows:
Limited Access User Rights, if specified on the License Key, carry certain limitations and restrictions. Users logging in under Limited Access User Rights are allowed no more than 30
minutes of continuous operation, must be casual, occasional, transient users, may direct output only to a local (non-network) printer, and may not have access to Application Design,
System Administration, or Database Management utilities.

Further, users running under, Limited Access User Rights, are excluded from running up to four simultaneous sessions,

Finally, Limited Access users may be either “Named” or “Anonymous” but only one User ID may be designated as the “Anonymous” Limited Access user.

Several environmental variables are available to customize the limited user implementation and are as follows:

APPX_SESSION_WILL_EXPIRE_STR – can be used to override the default the session expiration message which reads “As a 'limited user', your session will expire in 1 minute...”

Note: The message is limited to 80 characters and any additional characters will be ignored.

APPX_LIMITED_USER_SESSION_TIME_LIMIT – can be used to override, shortened only, the 30-minute limited user session time limit

Note: The limited user session time can be shortened by up to 29 minutes thus, a value of 10 means the session will last for 10 minutes.

APPX_LIMITED_USER_EXPIRE_MESSAGE_TIME – can be used to override the time before the session ends that the session expiration message is shown to the user

Note: By default, the session expiration message is shown to the user is 1 minute before the session expires. This can be set in whole minutes only.

HTML Client APPX Application Development

During this current Appx R&D development cycle (i.e., for Appx 6.2.0 since the Appx 6.1.0 general release) the html client has been updated so it can be used to create/edit images and ILF code as well to debug ILF code. The html code editing capabilities can be used on earlier version of Appx such as 5.5.1 but has limitation since some functionality had to added to the engine thus that functionality isn’t available in the earlier Appx versions. As well, not all development functionality, that is available in the Java client, is available in the html client. See know issues below for further information.

Bugs Fixed

6.2.0:

The following bugs were addressed in this Release:

New Features/Enhancements

6.2.0:

The following features and enhancements were implemented in this Release:

Known Issues

  • In the image editor, the multi widget editor doesn’t detect the selected items on the screen in APPX versions prior to 6.2.
  • In the image editor, screens that use the first row as the title bar don’t show up correctly in APPX versions prior to 6.2.
  • In the ILF editor, the search, replace and jump button items are not functional (We expect to deal with this issue in the next release)
  • In the ILF editor, some audit information will be truncated or missing (We expect to deal with this issue in the next release)
  • In the ILF editor, the ILF code end marker [END] will not be present on APPX versions prior to 6.2.0
  • In the ILF editor, statement(s) commented as a multi-line comment, will not be shown as being commented on APPX versions prior to 6.2.0
  • The cross reference tool screen (i.e., under Tools->Cross Reference->ILF Statements) is missing the ILF verbs and shows extra and missed formed text in APPX versions prior to 6.2.0
  • When selecting ILF code statements, the highlighting maybe be misapplied if the page keys are used in APPX versions prior to 6.2.
  • When changing FMS groups passible loss of data, see Bug #4901, as a reminder, always work with a backup copy of your data when changing FMS groups.

For an up to date list of known issues, use Bugtracker & search for bugs in Release 6.2.0. These are the known bugs that we expect to fix in the patch release.

Comments:

Read what other users have said about this page or add your own comments.



-- BrianRyan - 2022-04-13

Edit | Attach | Watch | Print version | History: r62 < r61 < r60 < r59 < r58 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r62 - 2022-05-24 - BrianRyan
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback