Custom Form Dependency Issues When Loading Existing Request Inputs - VCF Automation

Products

• VCF Automation

Issue/Introduction

• VCF Automation functionality for evaluating form input dependencies (e.g., <input_field_A>, <input_field_B>, <input_field_C>, <input_field_D>) fails to offer available values for dependent inputs (e.g., <dependent_input_field>)

• The issue specifically occurs when loading inputs from existing/previously saved requests in VCF Automation

• Dependency evaluation appears to be incorrectly processed upon loading request data, resulting in no values being offered for the dependent field

• The functionality remains operational when manually changing inputs (e.g., changing the <input_field_D> field triggers the <dependent_input_field> values to load)

• Switching the input back to the original value results in the <dependent_input_field> values failing to load again, likely due to request caching

Environment

• Product: VCF Automation
• Version: 9.1.0.0
• Component: Custom Forms / Blueprints

Cause

A caching regression was introduced in the Custom Forms service logic. When dependent fields are updated, the service fails to invalidate the existing cache or initiate a new request for the latest inputs. As a result, the form component serves outdated cached data instead of executing the external VCF Operations Orchestrator action required to populate the field with fresh values. This behaviour is triggered in specific dependency configurations and corner cases.

Resolution

This issue will be addressed in a future release of VCF Automation 9.x

Workaround: 

1. Manual Field Re-selection:

   • After the form has loaded and the dependent field appears empty or stale, manually re-select one of the upstream fields that acts as an input to the broken action. This forces a re-trigger of the action and populates the dependent field.

2. Input Configuration Modification:

   • Edit the Custom Form definition for the affected action.

   • Modify the action configuration to include the latest populated dependent field as an additional input. This configuration change explicitly links the dependency chain, forcing the system to re-evaluate the action when the field is updated, bypassing the stale cache.

Additional Information

This issue is specific to the dependency evaluation mechanism within VCF Automation Custom Forms. For further assistance or to track the status of the planned fix, please reference the case number or check the official Broadcom Support Portal release documentation.