docs(turbosign): document per-field default values and fixed date fields - #145
Merged
Conversation
yacinekahlerras-turbodocx
marked this pull request as ready for review
August 11, 2026 17:24
The field properties panel gained a "Default Value" editor for the six identity field types, and Date fields gained a "signing date vs fixed date" control. Two doc claims were wrong and are corrected here. - "Signature, Initials, and Date fields cannot have default values" was true for signature/initials but is no longer true for Date. - The API reference said a date field "can set defaultValue to 'today'". That was never true (the backend rejected any defaultValue on a date) and "today" is not special-cased anywhere — a date default must be a real MM/DD/YYYY string. Adds the second way to reach a default (click the field itself, not just the accordion) and notes that the six identity types share one value per recipient while Text stays per-field. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
amitsharma-turbodocx
force-pushed
the
docs/field-default-value
branch
from
August 20, 2026 15:33
00e2be0 to
7a94769
Compare
The per-language SDK reference pages showed DATE signature fields with no defaultValue, so the new fixed-date capability (a MM/DD/YYYY default that pre-fills instead of the signing date) was undiscoverable at the SDK-doc layer. Add a fixed-date example to the date field in each of the six SDK pages and extend the defaultValue property row to document the date format. The detailed contract still lives in the API Signatures field-types reference these pages link to. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ar date The backend now rejects a non-existent date (e.g. 02/31) on a DATE field's defaultValue with 400 InvalidDateValue, not just a format check. Spell that out in the API reference so SDK/n8n/API callers know the exact contract. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ules - Note the 600-character max on the defaultValue field-properties row. - State that signature/initial fields cannot carry a defaultValue. - State that a date field cannot be isReadonly (a pinned date still shows to the signer; it is not locked). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
3 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.
Related
Issue: nicolasiscoding/RapidDocxFrontEnd#1678
Frontend PR: nicolasiscoding/RapidDocxFrontEnd#2264
Backend PR: nicolasiscoding/RapidDocxBackend#1708
What this changes
TurboSign's field properties panel (the right panel when you click a placed field) gained a Default Value editor for the six identity field types, and Date fields gained a "Use the signing date / Use a fixed date" control. This documents both, and corrects two claims that were wrong.
Two corrections
1.
Setting up TurboSign.md— Date fields can have a default now.The note read:
True for signature/initials, no longer true for Date. Rewritten to keep the signature/initials rule, explain that a Date field fills with the signing date automatically, and point at the new section for pinning a specific date.
2.
API Signatures.md— the"today"keyword never existed.The API reference read:
This was never true: the backend rejected any
defaultValueon a date field withDefaultValueNotSupported, so the documented call would 400. It is also not true now — a date default must be a realMM/DD/YYYYstring, and"today"is special-cased nowhere in the backend or the signing page, so sending it would print the literal word "today" in the signed PDF.Replaced with the actual contract: omit
defaultValue(or send"") for signing-date behavior; sendMM/DD/YYYYto pin a date.Additions
Screenshots
Two new images, captured at 1355×812 to match every existing screenshot in this guide:
SetDefaultValueOnField.pngSetDateFieldValue.pngVerification
The behavior documented here was verified end-to-end against a local stack (isolated worktree, own database): defaults set from the panel appear in the accordion and vice versa, persist to
SignatureField.defaultValue, and pre-fill on the signing page. A fixed date of12/31/2026rendered as12/31/2026on the signing page rather than the signing date.Deployment Notes
Docs-only. No migration, no env var, no API change in this repo.
🤖 Generated with Claude Code