When re-running/retrying an IDP workflow that uses conditional inputs (e.g., fields that depend on connectionType), values from the previous selection remain in the workflow form data. This causes the Review step to show fields from both the old and new selections, which is confusing and can lead to incorrect submissions.

• Workflows with conditional parameters (dependencies / oneOf / if-then) behave correctly while filling the form.

• However, on Retry/Re-run, if the user changes the selector (e.g., azureblob → documentdb), the previous branch fields remain in the underlying formData.

• The Scaffolder Review page reads from the full formData, so it displays “old + new” fields together.

On Retry/Re-run, when the user changes a dependency-driving field (like connectionType), fields not in the active schema branch should be removed from the form data so only the current branch appears on Review and is submitted.

• Confusing UX during Review

• Higher risk of submitting stale/irrelevant parameters

• Common use-case for connection/config workflows (Azure Blob vs Cosmos DB vs SQL, etc.)

Enable (or provide a supported configuration option to enable) RJSF behavior that removes inactive fields from formData, such as:

• omitExtraData

• liveOmit

so that hidden/inactive fields do not persist across Retry/Re-run and do not appear on Review.