Data Transformation Task Checks

PowerDesigner provides default model checks to verify the validity of data transformation tasks.

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 data transformation action	At least one data transformation action should be associated with the data transformation task. Manual correction: Add any missing data transformation actions in the Actions tab of the data transformation action property sheet Automatic correction: None
Existence of data input	At least one data input should be associated with the data transformation task. Manual correction: Add any missing data inputs in the Inputs tab of the data transformation action property sheet Automatic correction: None
Existence of data output	At least one data output should be associated with the data transformation task. Manual correction: Add any missing data outputs in the Outputs tab of the data transformation action property sheet Automatic correction: None
Existence of data flow	At data transformation task should contain at least one data flow between each transformation step in the data transformation diagram. Manual correction: Add any missing data flows in the data transformation diagram Automatic correction: None