docs(turbosign): split Conditional Fields into UI and API/SDK sections - #151
Merged
Merged
Conversation
The page was API/SDK-only, which buried the fact that conditional fields can be built in the app. Restructure into a shared concept intro, an 'In the app' how-to with annotated screenshots, the existing API/SDK reference, and a UI-to-API crosswalk table.
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
1 participant
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.
What & why
The Conditional (IF/THEN) Fields page was written entirely for API/SDK developers — metadata contract, code samples, validation — with no path for someone setting conditional fields up in the app. A reader who builds documents in the TurboSign UI had nothing to follow.
This splits the page cleanly by audience while keeping all the existing API content:
Screenshots
Captured with
/guidewright-captureagainst the live app; walked with/guidewright-reviewfirst. Every screenshot uses an ACME Inc sample document and recipient — no customer or environment data.01-field-editor.png— the Assign Fields editor + palette02-add-fields.png— palette with Checkbox and Text highlighted03-rule-builder.png— the "Only show this field sometimes" rule builder highlightedNotes
ConditionalFieldSettingscomponent (Ticked / Not ticked, Hidden / Visible-but-not-fillable), so the crosswalk is accurate.@acme.com.