The APPX 4.2.6 Patch Release addresses the following items:
- Bug #1424: AT FIELD statement can be added in invalid Event Points
- Bug #1426: Export/Import Application to a Single-File fails
- Bug #1444: Changing Named Resource fails to build new EM
- Bug #1445: Java Client does not always detect server resource changes
- Bug #1448: Widget Sync utility must be required on upgrade
- Bug #1451: APPX_PRT_SCRIPT skipped when PRINT MODE=HOLD
- Bug #1476: Java Client slow over low bandwidth connections
IMPORTANT: If you are upgrading from a release prior to 4.2.5, please refer also to the 4.2.5 Release Notes, as a large quantity of changes, corrections, and enhancements were included in that release. As always, it is highly recommended that you review the Release Notes for all intermediate releases if you are not upgrading incrementally.
Bug #1424: AT FIELD statement can be added in invalid Event Points
- AT FIELD statements are only valid in Option Intercept and Global Option Intercept. A designer should get a 'Warning - This statement has no effect in this event point' message if you add it elsewhere. The warning did appear in non-image event points, but not in Pre-Display, Pre-Display/Verify, or Verify.
- This has been fixed in 4.2.6 to display the warning in all invalid event points.
Bug #1426: Export/Import Application to a Single-File fails
- When exporting an application to a Single-File (e.g. for transfer from Linux to AIX) the application could not be imported back. The import silently ended within 1-2 seconds and has NOT imported the application.
- This has been fixed for 4.2.6.
Bug #1444: Changing Named Resource fails to build new EM
- Changing a Named Resource record did not cause any related EMs to be rebuilt.
- This has been corrected for 4.2.6.
Bug #1445: Java Client does not always detect server resource changes
- The java client did not always detect that a server-side resource had changed and needed to be re-cached.
- Client detection and cache clearing of server side resources that have changed has been tightened for 4.2.6 to resolve this problem.
Bug #1448: Widget Sync utility must be required on upgrade
- In prior releases, the designer would be prompted to run the Widget Sync utility when it detected an application with old widget records. The designer had the option to skip running it and continue designing. If the designer opted not to run the utility and did some design work, then later tried to run the utility, it would fail since some of the fields it needs to update were already filled in.
- This has been changed to prevent access to application design in 4.2.6 if the Widget Sync utility has not been run.
Bug #1451: APPX_PRT_SCRIPT skipped when PRINT MODE=HOLD
- APPX was not invoking the APPX_PRT_SCRIPT (or any script) when a PDF report was spooled with PRINT MODE = HOLD. APPX did invoke APPX_PRT_SCRIPT when spooling a text report with PRINT MODE = HOLD.
- This has been fixed in 4.2.6.
Bug #1476: Java Client slow over low bandwidth connections
- The java client was very slow over a 64K ISDN connection. This had gotten much worse with the 4.2 GUI application design screens.
- An inspection of the 4.2 client datastream found extra widget specifications being sent. Basically the pulldown menu widgets were being sent twice on a non-scrolling menu or input. On a scrolling input the pulldowm menu widgets were also sent again for each scrolling record in the screen. So, for example, viewing the scrolling list of input processes woud send 221 widgets instead of the 79 required. Eliminating this duplication dropped the raw data being sent for the input process scroller from 44K to 25K. This is fixed for the 4.2.6 engine release.
- NOTE: All GUI input and menu processes that have pull-down menus should benefit from this change.