Using the AESection Class

The AESection PeopleCode class enables you to change the properties of an Application Engine program section dynamically, without having to modify any of the Application Engine tables directly. This capability enables you to develop rule-based applications that conform dynamically to variables that a user submits through a page, such as the Application Engine Request page.

The AESection class provides the following flexibility:

• Portions of SQL are determined by checks before a run.

• The logic flow conforms as rules change, and the program adjusts to the rules.

When using an AESection object:

• Ensure that you require primarily dynamic capabilities with the SQL your program generates.

• Ensure that the rules to which your program conforms are relatively static or at least defined well enough that a standard template could easily accommodate them.

• Consider using SQL definitions to create dynamic SQL for your programs to avoid the complexity created by the AESection object using the StoreSQL function.

• The AESection class is designed to dynamically update SQL-based actions only, not PeopleCode, Call Section, or other actions.

  You can add a PeopleCode action to your generated section, but you cannot alter the PeopleCode.

• The AESection class is designed to use for online processing.

  Typically, dynamic sections should be constructed in response to a user action.

Note:

Do not call an AESection object from an Application Engine PeopleCode action.