Use Custom Field Answers in Conditional Logic

Yuvin Kim

2026/11/12

Use Custom Field Answers in Conditional Logic

Yuvin Kim

2026/11/12

Your Custom Field collects a project’s estimated team size and whether it needs a system integration. The next questions should depend on those values: integration requests need technical details, and teams of 50 or more need a rollout question. Some respondents need both.

Walla conditional logic can route respondents using a property inside a Custom Field answer. The important work is selecting the correct property and value type, defining a default destination, and testing what happens when more than one condition applies.

This guide uses one fictional project-scope field to show the workflow. It includes copyable ChatGPT or Claude requests, a complete route map, boundary tests, and a check of the saved answers. The routing gathers information; it does not approve an integration or automatically assign a sales representative.


1. Choose the saved properties that will drive the routes

Connect Walla to ChatGPT or Claude before requesting changes. Read the English connection guide. You can build a Custom Field, review it, and approve a registered version before placing it in a form. Custom Fields guide


For this example, the requested Project Scope field saves a nested object with the following properties. These names are a proposed design, not a fixed schema for all Walla Custom Fields.


Saved property path

Type

Rule

scope.estimatedSeats

Number, integer

Required, from 1 to 500.

scope.needsIntegration

Boolean

An explicit Yes or No selection, saved as true or false.

questionVersion

String

project-scope-v1 for this example.

Use the actual field output schema to find the property you can compare. A label such as “Needs integration?” is not the same thing as its saved key, and the displayed word “Yes” is not necessarily the stored value.


The editor’s sub-answer selection supports choosing properties inside custom answers. The detailed guide also explains selecting array positions where applicable. This example uses a simple nested object and does not require an array index. Detailed sub-answer guidance, in Korean


2. Define the complete form before adding conditions

Question

Content

Who answers it

Q1. Test case ID

Required short text for fictional testing.

Everyone.

Q2. Project scope

Required Custom Field with estimated seats and integration choice.

Everyone.

Q3. Integration details

Which system do you want to connect, and for what purpose? Long text, required when reached.

Respondents with needsIntegration equal to true.

Q4. Team rollout

How would you roll this out across the team? Long text, required when reached.

Respondents with estimatedSeats of at least 50.

Q5. Additional notes

Optional long text, then submit.

Everyone.

Keep Q3 and Q4 in separate groups if you use grouped presentation. A jump into a group can display other questions in that group, so the grouping must agree with the intended routes.


The initial Custom Field should remain incomplete until both inputs are answered. A legitimate false means “No integration”; a missing property means the answer is incomplete, not that the respondent selected No.


3. Copy this Custom Field build request

Use Walla to prepare a Project Scope Custom Field in [workspace name or ID]. Check whether a suitable registered field already exists, inspect its actual output schema, and reuse it if it matches the required behavior. Do not change production form placements.


For a new build, show an Estimated seats input accepting integers from 1 to 500 and a Needs integration? Yes/No selection. Start both unanswered. Require an explicit choice; save Yes as boolean true and No as boolean false, not text.


Request a saved object with scope containing estimatedSeats and needsIntegration, plus questionVersion equal to project-scope-v1. Use Walla’s supported value and validation contract. Blank, invalid, or reset inputs must not leave a stale valid answer available for submission.


Show a review preview, the actual output schema, and the stored property paths and types we can use in conditional logic. Explain any unsupported part. Wait for approval before registering a new build, and do not publish a form.


Test the field’s inputs and saved-value design before using them as routing conditions. A number shown inside a custom interface is not automatically the property that the form’s logic evaluates.


4. Approve and create a draft branching test form

I approve the reviewed Project Scope build. Register it and create a new draft form named “Custom Field Branching Test” in [workspace name or ID]. If we are reusing an already registered field, use the agreed version instead of creating a duplicate.


Create these questions in order: Q1 Test case ID, short text, required; Q2 Project scope, the approved Custom Field, required; Q3 Integration details, long text, required when reached; Q4 Team rollout, long text, required when reached; Q5 Additional notes, long text, optional. Put Q3 and Q4 in separate groups if using grouped presentation.


Read back the actual form ID, question IDs, Custom Field version, output schema, and any existing logic. Do not invent question IDs or property paths. Keep the form unpublished. If a requested step cannot be performed with the available tools, explain the remaining editor step.


5. Add the routes in this order

Walla uses conditional destinations and a default path. Build the complete flow rather than adding a single “if integration, go to Q3” rule and leaving the rest to question order. Read the English Logic guide


Evaluate after

Condition and priority

Destination

Q2

First: scope.needsIntegration equals boolean true.

Q3.

Q2

Second: scope.estimatedSeats is greater than or equal to numeric 50.

Q4.

Q2

Default when neither condition matches.

Q5.

Q3

scope.estimatedSeats is greater than or equal to numeric 50.

Q4.

Q3

Default.

Q5.

Q4

Default.

Q5.

Q5

Default.

Submit.

The integration condition comes first because a matching route is selected before a later one. A respondent needing both follow-ups first answers Q3, then the condition after Q3 sends them to Q4. Without that second check, one matching condition could make the other required follow-up disappear.


Copy this logic-configuration request

In “Custom Field Branching Test” with form ID [test form ID], read the current question IDs and Q2’s actual output schema before editing. Use stored answer paths scope then needsIntegration, and scope then estimatedSeats, only if those paths and types are confirmed.


Configure Q1 to continue to Q2. After Q2, put these routes in priority order: first, Q2 scope.needsIntegration equals boolean true, go to Q3; second, Q2 scope.estimatedSeats is at least numeric 50, go to Q4; otherwise go to Q5.


After Q3, go to Q4 if Q2 scope.estimatedSeats is at least 50; otherwise go to Q5. After Q4, go to Q5. After Q5, reach submit. Preserve a default path at every routing point. Do not leave Q3’s default set to the next physical question, because integration-only respondents should skip Q4.


Use the supported conditional-logic editing tools. Compare a custom answer’s selected property against a typed literal, not a serialized whole object or its display label. Read the stored logic back and summarize each condition, priority, property path, value type, and destination. Keep the form unpublished. If a tool cannot set a condition, identify it and explain the exact editor action instead of reporting success.


6. Check property paths and value types in the editor

  1. Open Logic and choose Q2 as the reference question. For the integration comparison, select the nested scope property and then needsIntegration, and compare it with boolean true.

  2. For the team-size comparison, select scope and then estimatedSeats, choose the at-least numeric comparison, and enter the number 50.

  3. Check the owning routing question as well as the referenced answer: the team-size condition after Q3 still reads the earlier Q2 answer.

  4. Confirm each default destination. The default from Q2 is Q5, and the default from Q3 is also Q5.

  5. If a property is unavailable for conditions or the schema changed, correct the field version or condition rather than treating the whole Custom Field as a text answer.

The nested paths in this tutorial correspond to two property keys: scope, followed by the leaf key. Do not enter the dotted label as a single key unless the actual schema literally declares that key.


A missing path or unanswered value does not become a match just because you use a negative comparison such as “not equal”. Keep required-answer validation separate from the default route. In this example, an incomplete Q2 should block progress rather than silently becoming a standard request.


7. Run the four main combinations and boundary tests

All valid routes start with Q1 and Q2. The expected follow-ups below are fictional test cases to run on the actual form.


Estimated seats

Integration choice

Expected path after Q2

49

false / No

Q5 → submit

50

false / No

Q4 → Q5 → submit

49

true / Yes

Q3 → Q5 → submit

50

true / Yes

Q3 → Q4 → Q5 → submit

1

false / No

Q5 → submit

500

true / Yes

Q3 → Q4 → Q5 → submit

Also test blank seats, a missing integration choice, 0 seats, and seats above 500. Those inputs fail Q2’s validation; the default branch is not a substitute for correcting them.


Test changing an answer after visiting a branch
  1. Start with 50 seats and Yes, then return to Q2 and change to 49 seats and No. The final path should skip both Q3 and Q4.

  2. Start with 49 seats and No, then change to 50 seats and Yes. Both follow-ups should be reachable and required when reached.

  3. Start with 50 seats and Yes, then change only integration to No. Keep the rollout follow-up and skip integration details.

  4. Leave every unrelated branch question unanswered and confirm that it does not block a valid route’s submission.

  5. Repeat on a phone and in the actual grouped presentation or website embed you plan to use.

Returning to change a response may leave earlier branch answers in the stored record. Check the actual behavior instead of assuming skipped answers are automatically erased. Interpret the final route from the final Q2 values, and decide how your reporting process handles any stale follow-up values.


8. Publish only the test form and inspect saved responses

Publish only “Custom Field Branching Test” with ID [test form ID] and return its respondent link for fictional submissions. Do not publish or modify another form.


Submit BR-001 with 49 seats and No, BR-002 with 50 seats and No, BR-003 with 49 seats and Yes, and BR-004 with 50 seats and Yes. Complete the follow-ups each route reaches. Use another record, BR-005, for the change from 50/Yes to 49/No before submission.


Check each record in the form’s Response Sheet and response details. If needed, inspect a CSV or XLSX export. Read the English Response Sheet guide


Record

Final Q2 values

Applicable follow-up answers

BR-001

49 / false

Q5 only; no Q3 or Q4 needed.

BR-002

50 / false

Q4, then Q5.

BR-003

49 / true

Q3, then Q5.

BR-004

50 / true

Q3 and Q4, then Q5.

BR-005

49 / false after editing

Neither follow-up applies; inspect any earlier saved values separately.

Copy this verification request

In form [test form ID], inspect the final stored Q2 Custom Field values for BR-001 through BR-005 using the actual output schema. Report estimatedSeats as a numeric value and needsIntegration as a boolean where types are exposed.


Compare BR-001 49/false, BR-002 50/false, BR-003 49/true, and BR-004 50/true with the expected routes. For BR-005, verify that the final stored answer is 49/false rather than the earlier 50/true, and report whether previous Q3 or Q4 answers remain.


Check the applicable follow-up answers and any unexpected values, but do not claim the screen-by-screen route was proven from stored answers alone. Use the manual route tests to confirm what appeared and what was skipped. Do not edit or delete responses. Leave unavailable values unverified.


Use the response ID, final Custom Field answer, manually observed route, and relevant follow-up answers together as the test record. This separates whether the logic was configured, whether the respondent actually saw the intended questions, and whether the final answers were stored.


9. Recheck routing after a field revision

If a new field version renames a property or changes a number into text, existing comparisons may no longer refer to a supported value. Inspect the placed field’s schema and the configured paths after revisions, then repeat the threshold and answer-change tests.


Keep the first rollout small: one Custom Field, two clear conditions, explicit defaults, and four main test combinations. Use the English Logic guide and Custom Fields guide while building the workflow through conversation.


Open Walla to build your conditional form