You can modify unsupported code by following the instructions in Workarounds for Unsupported Features in Workarounds & APIs Guide. The Guide provides examples of some common unsupported features and ways to work around them.
The following two modification methods are included in Workarounds & APIs Guide, and worth highlighted here because of their importance:
-
(EAServer only) Encapsulating unsupported features into PowerBuilder non-visual user objects (NVOs) and deploying the NVOs to Appeon Server.
This method can work around a vast number of unsupported features (both browser limitations and Appeon limitations). Refer to the section called “Moving unsupported features to Appeon Server as n-Tier NVOs” for instructions on this method.
-
(Windows only) Using the Appeon workaround for distributed DataWindows.
Appeon Workaround PBL provides two objects appeondatawindow and appeondatastore, and four functions GetFullState, SetFullState, GetChanges and SetChanges, for supporting distributed DataWindows. Refer to the section called “Migrating distributed applications with distributed DataWindows” for instructions on this method.