Difference: APPX500BugsFixes (4 vs. 5)

Line: 1 to 1

META TOPICPARENT	name="APPX500"

Changed:

<
<

APPX 5.0.0 Bug Fixes

>
>

Changed:

<
<

Following is a list of bugs that were fixed in Appx release 5.0.0.

>
>

Following is a list of bugs that were fixed in Appx release 5.0.

Line: 335 to 335

- A C-assert 'can't write widget record - error - already on file' occurs in Language Translation
Misleading Error message from Apply Patch (#2244)
- If you try to 'Apply Patch' or a normal Design Transfer but the source files don't exist, instead of APPX saying it couldn't find the application files, you get an error saying 'Application Lock does not allow Transfer Out operations'. This is completely misleading.

Added:

>
>

The appxODBC interface, which was broken in 5.0.0, has been fixed for all platforms. (#2347)
The Oracle interface did not work on HP PA Risc platform; it has been fixed. (#2348)
The uappxd connection manager did not honor startup process options when they are specified on the java client command line; this has been corrected. (#1485)
An error message was appearing when Help was selected for the Random Key Generation button in Database Management and FMS Controls; this has been fixed, and the Help text now appears properly. (#2381)
The Workstation address was missing from the View License Usage image in System Registration; this has been fixed. (#2386)
Audit History was not recording properly if multiple changes were made to multiple processes without exiting the process editor; this has been corrected. (#2389)
Repainting of scrolling screens has been fixed, to overcome a problem where not all records were being repainted. Also, display of parent screens after returning from a child process has been fixed to always repaint the parent records. (#2396, #2397)
The pull-down list for defining field types for work fields was not displaying; this has been fixed. (#2398)
An experimental algorithm for sorting child processes was inadvertently activated in earlier version 5 releases. It is turned off in 5.0.2; for releases 5.0.0 and 5.0.1, the environment variable APPX_OLD_CHILD should be set equal to the value 1 to prevent potentially serious unintended effects.

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