Use Single-Line and Multi-Line Text Fields

Use Single-Line Text for short answers that must fit on one visible line, and Multi-Line Text for longer responses that need line breaks and wrapping. Both are signer-input fields and must resolve to the correct participant before the Request is sent.

Choose the Right Text Field

  • Single-Line Text — best for short values such as an ID, department, short answer, or reference. The current signer app keeps the entry on one line.
  • Multi-Line Text — best for comments, explanations, descriptions, or other responses that need multiple lines and wrapping.

Place, Size, and Assign the Field

  1. Place the text field on the intended PDF page.
  2. Resize it for the amount of signer input you realistically expect.
  3. Give it a clear label/accessibility name.
  4. Assign it to the correct signer role before the Request is sent.
  5. Set Required only when the signer must provide a value before completion.

Single-Line Text Enforces the Visible Width

The current 2.0.7 signer app measures Single-Line Text against the rendered input width. If the next keystroke would make the text exceed the available one-line area, QCDS restores the last value that fit and tells the signer that the line is full.

The server also normalizes whitespace in Single-Line Text and bounds the stored text. In practice, the visible field width is the important customer-facing limit, so make the field wide enough for the expected answer.

Multi-Line Text Accepts Longer Responses

Multi-Line Text uses a textarea in the signer experience, preserves multi-line input for rendering, and allows a substantially larger stored value than Single-Line Text. Current server normalization bounds Multi-Line Text at 12,000 characters.

Field size still matters. A large server-side character allowance does not mean every long answer will be visually appropriate in a small PDF rectangle. Test realistic content before using a compact field in production.

Required-State Behavior

For either type, a Required field must contain a non-empty value before the signer can submit. Optional text fields may remain blank. QCDS autosaves active signer input as the participant works.

Verify With Realistic Test Data

  1. Create a test Request from the published Template.
  2. Enter a realistic maximum Single-Line value and confirm it fits the intended width.
  3. Enter several lines in the Multi-Line field.
  4. Confirm Required behavior works as intended.
  5. Complete the Request and inspect the final PDF for readable placement.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDS feature? Visit the QC Digital Signature Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.