Action Pages
Action pages are the Active Server Page (ASP) pages that constitute a module. Action pages can be used for pure-processing; that is, they are not responsible for the display of any user interface.
In contrast, many action pages are directly responsible for the user interface displayed in the content pane of Commerce Server Business Desk. There are two main types of action pages that are responsible for the display of the user interface: list pages and edit pages.
Any action page linked to as a module or task entry point must be registered in a module configuration file.
At a minimum, action pages responsible for the display of the content pane are comprised of the following:
Directives to include the appropriate Business Desk utility files. Some module-specific utility files might also be included.
The Business Desk customizable style sheet (CSS), which provides a consistent set of styles for a particular instance of Business Desk, as well as the styles required by the Business Desk HTML Components (HTCs).
A call to one of the Framework utility functions, InsertTaskBar or InsertEditTaskBar, to display the task buttons specified in the module configuration file for this action.
One or more HTML forms, sometimes including one or more HTCs, that specify the user interface elements associated with the action.
Although the editing HTCs must generally be within the forms; non-editing controls (like the ListSheet HTC) need not be.
Optionally, the ASP code that processes the form data upon submission of the form. This code can be on the same action page, or can be on a different ASP page of either the pure-processing variety or the user interface variety, depending on how the tasks are configured. Typically, if the same page is to be displayed after some ASP code is executed, the form associated with the task will post to that same page and the ASP processing will be done at the top of the page before the content is redisplayed.
This section contains: