Difference: Appx620Features (55 vs. 56)

Revision 562022-05-16 - MisaghKarimi

  APPX 6.2.0 Features 

This page provides an overview of the new features in APPX 6.2.x
 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, 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.
->
>
+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
->
>
+ JSON Parser APIs
-<
<
+The parser can now parse a file of JSON data, the parsing size limits have be removed and the parsing results can be optioanlly converted to Unicode.
 APPX Data Services API
->
>
+You can use the following APIs to parse a JSON file or string:
-<
<
+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.
->
>
+ --- .JSON PARSE
 --- .JSON PARSE FILE
 XML Writer APIs
-<
<
+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.
->
>
+You can use these new APIs to create a well formatted XML file.
-<
<
+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.
->
>
+ --- .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.
  Cross-Reference for file - not find 'Write' (#5007)
  Win-SSO doesn't appear to work with Windows Server 2012 2012R2 (#3013)
  Recovered encrypted file is corrupt (#4849)
-<
<
+ ADC Hangs On Starup If -user and -password is provided (#4947)
->
>
+ ADC Hangs On Startup If -user and -password is provided (#4947)
  APPX Doesn't Find Constraint Records (#4956)
  Client Type Column In Missing on Session Monitor (#4962)
  APPX System Error During Restructure on Risc Platforms (#4965)
  Table on popup with same relative position as table on parent equals c-assert (#4984)
  Fields with Picture Widgets Don't Print On PDF Reports (#4986)
  Multi Widget Editor Clears GUI Copy/Cut Buffer (#4987)
-<
<
+ Odd ILF behaviour while line numbers are showing? (#4996)
->
>
+ Odd ILF behavior while line numbers are showing? (#4996)
  HTML Client Doesn't Display EM Errors (#5000)
  Entering Large Unicode Data Causes Crash (#5002)
  Table Process Crashes On Large Raw Fields (#5005)
  .TEXT INSERT AT POS Subroutine Has Difficulty With The Last Character (#5009)
  IF EX statement On Unicode Field Doesn't Set --- TEXT AT POSITION (#5013)
  Table Widget not possible on MENU (#5014)
-<
<
+ .TEXT UPPER TO LOWER with Fristword Flag Issue (#5017)
->
>
+ .TEXT UPPER TO LOWER with Firstword Flag Issue (#5017)
  Cross-reference – ILF Statements for Html client missing Ilf verbs, has extra title bar text and mal-formatted literal text (#5019)
  INVOC PROC process has 2 default buttons (#4964)
  Scan list build hangs on Direct Process (#5010)
 The following features and enhancements were implemented in this Release: 
 Add API Subroutines for XML Writer Calls (#618)
-<
<
+ Enahncements to JSON Parser (#619)
->
>
+ Enhancements to JSON Parser (#619)
  Implement Limited Access User Rights as defined in the APPX License Agreement and CUSTOMER PRICE LIST dated 1/1/2008 (#629)
  Updating appxLoginMgr startup script on Linux/Unix (#630)
  Add an informational popup screen/status message to the disposition process. (#631)
  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 Referenece->ILF Statements) is missing the ILF verbs and shows extra and missed formed text in 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.
 

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.

View topic | History: r99 < r98 < r97 < r96 | More topic actions...