Decision Checks

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

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.
Invalid decision	A decision represents a conditional branch when a unique flow is split into several output flows, or it represents a merge when several input flows are merged into a unique output flow. That is why a decision must have more than one input flow or more than one output flow. Manual correction: Add any missing flows on the decision Automatic correction: None
Event condition coherence	All conditions on outgoing flows must be of the same type. Condition types can be a Boolean expression or an event. A flow defined from a decision object to a receive activity is considered as an event that corresponds to the reception of a message. Manual correction: Assign the same conditions to all outgoing flows Automatic correction: None