Variable Checks

PowerDesigner provides default model checks to verify the validity of variables.

Check	Description and Correction
Name/Code contains terms not in glossary	[if glossary enabled] Names and codes must contain only approved terms drawn from the glossary. Manual correction - Modify the name or code to contain only glossary terms. Automatic correction - None.
Name/Code contains synonyms of glossary terms	[if glossary enabled] Names and codes must not contain synonyms of glossary terms. Manual correction - Modify the name or code to contain only glossary terms. Automatic correction - Replaces synonyms with their associated glossary terms.
Name/Code uniqueness	Object names must be unique in the namespace. Manual correction - Modify the duplicate name or code. Automatic correction - Appends a number to the duplicate name or code.
Undefined data type	The variable should have a defined data type. Manual correction: Set a correct data type for the variable in the Data Type list of its property sheet Automatic correction: None
Variable used out of scope	The variable must be used in the scope where it is defined. When a variable is used in a different package or composite process from the one where it is defined, a shortcut is created. The package or composite process that owns the shortcut must be a child of the package or composite process that owns the variable object. In other cases, the variable is not visible, as it is not defined in the parent scope. Manual correction: Move the variable under the common parent or duplicate it Automatic correction: Moves the variable under the common ascendant
Data type coherence	A variable mapped to a message should be of the same type as the message. Manual correction: Change the type of the variable to be the same as the messages to which it is mapped Automatic correction: Changes the variable type when it is mapped only once to a message or mapped several times but to the same message