[Quality Management] Init values in the test if there are two or more promoted quality results

[JakovljevicDusan]

What & why

Handle default condition in Test for blank value

Linked work

Fixes AB#622769

[github-actions]

$\textbf{🟡\ Medium\ Severity\ —\ Upgrade} \quad \color{gray}{\texttt{\small Iteration\ 1}}$

Empty condition silently overwrites on upgrade

Adding '' to the in list means any existing record whose Condition field is blank will now be treated as a default and overwritten during configuration seeding — even if the blank value was intentionally left by a user or previous customization. This silent data mutation can occur on every upgrade run that calls this code path with OnlyOverwriteIfADefaultCondition = true.

Recommendation:

• Confirm whether a blank Condition should truly be equated with the named default values. If so, document this assumption. If not, keep the guard to the three explicit default constants and handle blank conditions separately (e.g., only overwrite blank on fresh insert). At minimum, add a comment explaining why '' is included alongside the named defaults.

Suggested change

	if AlwaysUpdateExistingCondition or (OnlyOverwriteIfADefaultCondition and (ToTestQltyIResultConditConf.Condition in [QltyInspectionResult."Default Boolean Condition", QltyInspectionResult."Default Number Condition", QltyInspectionResult."Default Text Condition"])) then begin
	if AlwaysUpdateExistingCondition or
	(OnlyOverwriteIfADefaultCondition and
	(ToTestQltyIResultConditConf.Condition in
	// '' treated as uninitialized; safe to overwrite just like named defaults
	['',
	QltyInspectionResult."Default Boolean Condition",
	QltyInspectionResult."Default Number Condition",
	QltyInspectionResult."Default Text Condition"])) then begin

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why}