Updating Customizations
Whenever a new version of the application is installed, the customized programs in your local source code folder must be updated to the new version. In most cases, you can update the version number in the header of the program (&scoped-define class-version xx.yy) to the version number displayed in the new template folder. If the template file has undergone many changes since the previous version, it may be more useful to copy the template file and add your customizations again.
When you have reinstalled the application, you must compare the methods in your customizations with those contained in the new template files, because methods may change with every new version.
You must also evaluate the method descriptions and parameters, because parameters can also be removed between installations. You must resolve any differences before you continue with customization. Use a standard file diff tool to make your comparisons.
Running Other Business Methods
You can run any customizable procedure from within the customization, using a standard run statement.
The procedure itself can be customized or standard. The procedure is run within the standard business component through procedure overloading.
Example: In this example, you run the method GetCustomFieldList from within a customization of BItem.ValidateCustomFields:
/**/
PROCEDURE BItem.ValidateCustomFields.before:
define variable vcList as character no-undo.
define variable viReturn as integer no-undo.
run GetCustomFieldList (output vcList, output viReturn).
END PROCEDURE.
/**/