|
|
|
The primary method of applying naming standards is through an application identifier.
An application is a group of logically related functions and/or data. Every application is defined in the Application Register and named with a unique identifier. This application identifier provides a unique name space for application components.
Before you can define application components, you must define an application definition within the Application Register.
The following sections detail how individual application components are named.
Note: For applications that you define, ensure that the first character of the application identifier is Y. This provides name space protection from distributed product definitions and your applications.
The message prefix, specified within an application definition, must be the same as the application identifier.
The first three characters of the Panel identifier must be the same as the application identifier.
The first three characters of the procedure name must be the same as the application identifier.
The application identifier must be explicitly specified for Menus, Lists, Panel Domains, Help, Tables, and Criteria Definitions.
Note: The help function names OVERVIEW and INDEX are reserved for application overview help and the help index, respectively.
The first three characters of Message and Command identifiers must be the application identifier.
The first three characters of a report application identifier must be the same as the application identifier.
The Report Application Identifier must be explicitly specified within Report Definitions.
The first three characters of a Map Name must be the application identifier.
In addition to application components there are other entities that are visible outside an application and therefore require name space protection by prefixing their names with the application identifier. These include the following:
| Copyright © 2008 CA. All rights reserved. |
|