Naming Conventions

You can define naming conventions for your model objects in the Model Options dialog box. You can:

Set rules to enforce predefined name and code formats for all the objects within a model. When you type a name or a code that does not respect the conventions, PowerDesigner adapts them to the required format. See Name/Code Format.
Set conversion scripts in order to generate objects name from their code or objects code from their name using specific macros and conversion tables. This feature is only available when you select the Enable name/code conversion option. See Name and code conversion scripts.

Note:
The name into code conversion is particularly useful for inter-model generation, as it allows you to define how you want the codes of your model objects to be generated. For more information on the name into code conversion during the inter-model generation, see section on inter-model generation options in the different modules user's guides.

Name/Code Format
Name and code format encompasses constraints on length, character case and type for the name and the code of objects.
Name and Code Conversion Scripts
You can set conversion scripts in order to generate the name of an object from its code or vice versa using conversion scripts and tables. Name/code conversions can be applied to all named objects in a model or for each type of object individually.
Using a Conversion Script
Default conversion scripts allow you to generate names from codes and codes from names using macros. These are macros used in the Generation Template Language (GTL) and recommended for the name/code conversions.
Using a Conversion Table
Conversion tables provide a way to define a correspondence between the name and the code of an object or the code and the name of an object.
Defining a Code Naming Convention in a Resource File
When you define code naming conventions in a model, these are not automatically applied to the current model. To apply these code naming conventions, you have to do one of the following actions:

Parent topic: Customizing Your Modeling Environment