Transformation Control Flow Checks

PowerDesigner provides default model checks to verify the validity of transformation control flows.

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.
Existence of transformation start	At least one transformation start should be associated with the data transformation control flow. Manual correction: Add any missing transformation starts in the Starts tab of the transformation control flow property sheet Automatic correction: None
Existence of transformation end	At least one transformation end should be associated with the transformation control flow. Manual correction: Add any missing transformation ends in the Ends tab of the transformation control flow property sheet Automatic correction: None
Existence of control flow	At transformation control flow should contain at least one control flow between each start, end, transformation task execution and synchronization in the transformation control flow diagram. Manual correction: Add any missing data flows in the transformation control flow diagram Automatic correction: None