Designer-Invoked Processes

The runtime application contains several predefined processes. In general, these processes can be placed into two categories: processes that a designer can invoke, and processes that only APPX can invoke. Most of the predefined processes are only invoked by APPX.

Following is a list of the predefined processes that a designer can invoke (each of which is described in detail later in this chapter):

• APPX MENU, which allows a user to select a new database and provides access to system administration, application design, and database management.
• BEGIN LIVE OPERATIONS, which transfers the run phase from initial setup or recovery processing to live operations.
• CHECK GUI CLIENT, which determines if the current engine is connected to a GUI-enabled client.
• DISPOSITION, which allows a user to provide information that controls how and where a report is to print.
• ENTER BILLING CODE, which allows a user to enter a value into the predefined field BILLING CODE.
• GET CMD LINE PARM, which checks for the existence of a parameter on the command line used to invoke the current engine.
• GET ENV VAR, which retrieves the contents of an environment variable.
• GET FILE FROM CLIENT, which retrieves a file from the client system and stores it on the server.
• PROCESS QUERY RECORD, which potentially adds a PCF record to the result set of a query.
• SELECT DATABASE, which allows a user to select the appropriate database.
• SEND FILE TO CLIENT, which retrieves a file from the server and stores it on the client system.