Feature Request
F
Fairy tale Canidae
Feature Request: Dynamic Forms / Conditional UI Support in Harness IDP
Overview
We would like to request support for Dynamic Forms / Conditional UI behavior within Harness IDP workflows. This capability would significantly improve the usability of complex onboarding and provisioning workflows where form behavior needs to adapt based on runtime data and user input.
Log In
F
Fairy tale Canidae
What We Mean by “Dynamic Form / Conditional UI”
A dynamic form is one where the UI changes based on:
Server-driven data
UI elements (fields, sections, options) adapt based on data returned from an API.
Client-driven user input
UI adapts in real time based on selections made by the user.
Combination of both
API determines the available options, the user selects an option, and the UI conditionally renders additional fields or sections based on that selection.
Specific Use Case
Initial API Call
On form load, call an external API.
API returns an array of options (e.g., Option 1 / Option 2 / Option 3).
User Selection
User selects one of the returned options from a dropdown or radio button.
Conditional Rendering
Based on the selected option:
Show or hide specific fields
Render different sections of the form
Enforce different validation rules
Optionally trigger follow-up API calls
Example
Option A → Show Kubernetes-specific fields
Option B → Show GitHub repo configuration fields
Option C → Show Cloud/IaC-related fields
Why This Is Important
Reduces user confusion by showing only relevant inputs
Enables richer, context-aware workflows without creating multiple separate templates
Aligns IDP workflows with real-world, decision-driven onboarding and provisioning scenarios
Eliminates the need for workarounds such as separate workflows per option
High-Level Expectations (Flexible on Implementation)
We are open to different implementation approaches, for example:
Conditional rendering based on form field values
API-driven schema updates
Simple rule-based visibility (if/else conditions)
Dependency-aware form sections
The key requirement is the ability to dynamically control what the user sees based on API responses and user selections within a single workflow.