From 44cb78487bef50d12bd823d83a52a0d95d2c629b Mon Sep 17 00:00:00 2001 From: panchicore Date: Wed, 26 Aug 2026 07:56:49 -0500 Subject: [PATCH 1/3] Workflows: conditional required fields on User Action steps (sc-17682) 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 --- .../guide/workflows/_conditional-requirements.qmd | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/site/guide/workflows/_conditional-requirements.qmd b/site/guide/workflows/_conditional-requirements.qmd index a1cd90cfe..68326770f 100644 --- a/site/guide/workflows/_conditional-requirements.qmd +++ b/site/guide/workflows/_conditional-requirements.qmd @@ -52,6 +52,21 @@ Conditional requirements are required or optional for the following step types:^ **Toggle Optional** to ON if the field should be optional and not required. +- (Optional) Create conditional requirement groups so fields appear and become required only when certain conditions are met: + + i. Click **{{< fa ellipsis-vertical >}} ⋮** on the step menu and select **Add Conditional Group**. + + ii. In the dashed **Conditional Display Group** container that appears, click **Edit Conditions** and configure when this group should apply: + - Use the same `AND` / `OR` rule builder available elsewhere in workflows + - Conditions are evaluated against record or artifact field values + - Supported field types: checkboxes, single-select, multi-select, number fields, and date fields + + iii. Drag requested fields into the group container to make them conditionally required. When the rule matches, these fields will appear in the form with a caption explaining why, and they become required. When the rule does not match, the fields remain hidden and a note appears: *"[N] fields don't apply to your answers. Anything you entered is kept."* + + iv. At runtime, as users answer questions on the form, fields in conditional groups appear and disappear based on their answers. Required fields are enforced only while their group's condition is active — the form tells users what is still needed before they can submit. + + **Note:** Each workflow's audit trail records when a user's answers cause a conditional group to become active, providing visibility into what drove a particular set of field requirements. + - (Optional) Present these requested fields to users in steps: i. Click **{{< fa plus >}} Add Step** to add a step. From ed639c2c2c219959bdcb55c2a76731d4fed65654 Mon Sep 17 00:00:00 2001 From: panchicore Date: Wed, 26 Aug 2026 07:59:16 -0500 Subject: [PATCH 2/3] Drop unverified driver-type list; document the locked required switch inside groups MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 Claude-Session: https://claude.ai/code/session_01BmPREobo2AJE6PBnGkvWWC --- site/guide/workflows/_conditional-requirements.qmd | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/site/guide/workflows/_conditional-requirements.qmd b/site/guide/workflows/_conditional-requirements.qmd index 68326770f..18343c10d 100644 --- a/site/guide/workflows/_conditional-requirements.qmd +++ b/site/guide/workflows/_conditional-requirements.qmd @@ -59,9 +59,8 @@ Conditional requirements are required or optional for the following step types:^ ii. In the dashed **Conditional Display Group** container that appears, click **Edit Conditions** and configure when this group should apply: - Use the same `AND` / `OR` rule builder available elsewhere in workflows - Conditions are evaluated against record or artifact field values - - Supported field types: checkboxes, single-select, multi-select, number fields, and date fields - iii. Drag requested fields into the group container to make them conditionally required. When the rule matches, these fields will appear in the form with a caption explaining why, and they become required. When the rule does not match, the fields remain hidden and a note appears: *"[N] fields don't apply to your answers. Anything you entered is kept."* + iii. Drag requested fields into the group container to make them conditionally required. A field placed in a group has its required/optional switch locked — inside a group, requiredness is decided by the group's condition. When the rule matches, these fields will appear in the form with a caption explaining why, and they become required. When the rule does not match, the fields remain hidden and a note appears: *"[N] fields don't apply to your answers. Anything you entered is kept."* iv. At runtime, as users answer questions on the form, fields in conditional groups appear and disappear based on their answers. Required fields are enforced only while their group's condition is active — the form tells users what is still needed before they can submit. From 7cf3d04d8ca5705eab361f4c57c6829ef4065038 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Fri, 28 Aug 2026 01:14:34 +0000 Subject: [PATCH 3/3] chore: refresh chatbot product map --- site/llm/chatbot-product-map.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/llm/chatbot-product-map.md b/site/llm/chatbot-product-map.md index e446098f0..1d3625616 100644 --- a/site/llm/chatbot-product-map.md +++ b/site/llm/chatbot-product-map.md @@ -603,7 +603,7 @@ **Docs (related):** - `/guide/configuration/customize-your-dashboard.html` - - Sections: Prerequisites; Manage dashboards; Add dashboards; Edit or remove dashboards; Manage widgets; Arrange widgets; Add widgets; Remove widgets + - Sections: Prerequisites; Manage dashboards; Add dashboards; Edit or remove dashboards; Share a dashboard with your organization; Manage widgets; Arrange widgets; Add widgets - *No direct help link in frontend; related docs inferred from keywords.*