Dynamic vRO Actions Not Triggering on Single Parameter Change in VCF Automation 9.1

Products

• VMware Cloud Foundation

Issue/Introduction

In VCF Automation (formerly VMware Aria Suite), users leveraging custom created Blueprints with Custom Forms may notice different behavior in version 9.1 compared to Aria Automation 8.18.X. Dynamic vRO Actions used to populate Input Lists dynamically do not trigger when only a single input parameter changes (e.g., changing only the Project while the Region remains the same). In previous 8.X versions, changing a single input parameter was sufficient to trigger a new run of the vRO Action to fetch new parameters.

Environment

VCF Automation 9.1

Cause

In modern tenancy, VCF Automation utilizes Data APIs rather than external values. The Data API employs caching logic to prevent re-triggering actions when the provided data has not changed. If a parameter like projectId is passed but is not explicitly connected as an input to the custom vRO action, the system perceives no change in the connected parameters (e.g., region) and therefore does not trigger the action.

Resolution

Follow these steps for a workaround:

• Edit the custom vRO action utilized by the Custom Form.

• Add the projectId as an explicit input parameter to the vRO action.

• Pass the project ID parameter to the action to guarantee the Data API registers the parameter change and properly triggers the action.