From 29bc0cf8b576f6ecda7529eadc83002778d1a3ec Mon Sep 17 00:00:00 2001
From: TekH <h.tek@digitaldata.works>
Date: Fri, 27 Mar 2026 09:46:43 +0100
Subject: [PATCH] Relax RESULT validation to allow StatusId, Info, or Error

Previously, RESULT required a non-null StatusId. Now, validation passes if at least one of StatusId, Info, or Error is provided, making the requirements more flexible.
---
 .../Common/Validations/InsertObjectProcedureValidator.cs    | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/ReC.Application/Common/Validations/InsertObjectProcedureValidator.cs b/src/ReC.Application/Common/Validations/InsertObjectProcedureValidator.cs
index f205ea7..f4595d2 100644
--- a/src/ReC.Application/Common/Validations/InsertObjectProcedureValidator.cs
+++ b/src/ReC.Application/Common/Validations/InsertObjectProcedureValidator.cs
@@ -58,9 +58,9 @@ public class InsertObjectProcedureValidator : AbstractValidator<InsertObjectProc
                 .NotNull()
                 .WithMessage("RESULT requires ResultActionId (maps to @pRESULT_ACTION_ID).");
 
-            RuleFor(x => x.Result!.StatusId)
-                .NotNull()
-                .WithMessage("RESULT requires ResultStatusId (maps to @pRESULT_STATUS_ID).");
+            RuleFor(x => x.Result!)
+                .Must(r => r.StatusId != null || r.Info != null || r.Error != null)
+                .WithMessage("RESULT requires at least one of: StatusId, Info, or Error.");
         });
 
         // ENDPOINT_PARAMS validation