Dynamic table refresh fails in Aria Automation custom forms due to hidden required fields

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

An intermittent failure where dynamic tables within custom forms in VMware Aria Automation (8.18.1) and Aria Orchestrator (8.18.1) fail to refresh. Specifically, when a form tab (e.g., "Tier 2") is configured with conditional visibility based on another field (e.g., "Quantité N Tiers" > 1), the dynamic actions associated with tables inside that tab cease to execute once the tab becomes visible.

Working State:

The table’s dynamic behavior no longer works after applying the visibility condition to the “Tier 2” tab:

 

Environment

VMware Aria Automation 8.x
VMware Aria Orchestrator 8.x

Cause

The issue is caused by a logic deadlock within a hidden form field, typeBdd2, which prevents the execution of dynamic actions. Specifically:

Logic Conflict: The field is configured with a Visibility condition (Type (Tier 2) == BDD) and a broader Required condition (Type (Tier 2) == BDD OR Quantite N Tiers >= 2).

Validation Deadlock: When the "Tier 2" tab is revealed (e.g., Quantite N Tiers is set to 2), the field typeBdd2 remains Hidden but simultaneously becomes Required.

Action Suppression: Because the field is mandatory but invisible to the user, it remains null/empty. The Aria Automation form engine identifies this as an invalid field state and subsequently suppresses all dynamic actions (such as table refreshes) within that scope to prevent the submission of incomplete data.

Resolution

RESOLUTION: 

1. To resolve the dynamic action failure, the logic for the field typeBdd2 (Type BDD Tier 2) must be adjusted to ensure the field is never "Required" while it is "Hidden." This can be achieved through one of the following two methods:

Synchronize Visibility with Requirements:
Update the Visibility condition of the typeBdd2 field to include the quantity threshold.

Action: Add Quantite N Tiers >= 2 to the Visibility logic.

Result: This ensures that whenever the field becomes mandatory due to the tier quantity, it is also visible to the user, allowing the form to validate correctly.

2. Modify Required Constraints:
Remove the quantity-based mandatory requirement from the field logic.

Action: Delete the OR Quantite N Tiers >= 2 clause from the Required condition.

Result: The field will only be required when the specific type is set to "BDD," preventing a null-value validation error when the field is hidden.