Workflows: conditional required fields on User Action steps (sc-17682) - #1475
Open
panchicore wants to merge 2 commits into
Open
Workflows: conditional required fields on User Action steps (sc-17682)#1475panchicore wants to merge 2 commits into
panchicore wants to merge 2 commits into
Conversation
Added guidance for creating conditional requirement groups on User Action steps. Documented configuration (Edit Conditions, drag fields into groups), runtime behavior (fields appear/disappear, live requiredness, validation enforcement), and audit trail recording. Co-Authored-By: Claude Fable 5 <[email protected]>
|
|
… inside groups The supported-field-types enumeration wasn't grounded in the shipped PR (its test plan used date/text as member fields, which proves nothing about drivers) — the rule-builder reference already covers it. Added the one authoring behavior admins will notice: the required/optional switch locks for fields inside a group. Co-Authored-By: Claude Fable 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01BmPREobo2AJE6PBnGkvWWC
panchicore
marked this pull request as ready for review
August 27, 2026 18:15
Contributor
Validate docs site✓ INFO: A live preview of the docs site is available — Open the preview |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Added documentation for conditional requirement groups on User Action steps — a feature that lets workflow authors create groups of fields that appear and become required only when certain conditions are met.
Changes
Updated
site/guide/workflows/_conditional-requirements.qmd:The include is consumed by two pages:
guide/workflows/conditional-step-requirements.qmdtraining/administrator-fundamentals/using-validmind-for-risk-management.qmdBoth pages validated with quarto render.
UI labels used (source)
From validmind/frontend #2820 (config):
From validmind/frontend #2836 (runtime):
Release notes
documentationWorkflow User Action steps now support conditional required fields. Authors can group fields so they appear and become required only when answers on the form call for them — for example, asking for foundation model details only when someone answers "yes" to Uses Gen AI. Users filling the form see live feedback as their answers change, and the form enforces requirements only for fields that apply.
🤖 Generated with Claude Code
https://claude.ai/code/session_01BmPREobo2AJE6PBnGkvWWC