Use Request Text for Values That Change on Every Request

Request Text is fixed text that the sender supplies while preparing one specific Request. Put the field in a reusable Template when the location stays the same but the wording or value changes from transaction to transaction.

Unlike Document Text, Request Text is intentionally allowed to remain blank in the published Template. QCDS requires the sender to fill it before that Request can be sent.

Choose Request Text Instead of Document Text

  • Use Document Text when the wording belongs permanently in the reusable Template.
  • Use Request Text when the field position is reusable but the value belongs to one transaction—for example an order number, project name, property address, case reference, or other request-specific wording.

Both are creator-controlled document content. Signers can see the resulting text but do not edit or complete it.

Place Request Text in the Template

  1. Open the current Template draft in the visual builder.
  2. Place Request Text on the intended PDF page.
  3. Move and resize it like other builder fields.
  4. Leave its transaction value blank while designing the reusable Template.
  5. Save, Validate, and publish the Template.

Template publication does not require a Request Text value because that value is deliberately supplied later, when a sender uses the Template.

Enter the Value for a Specific Request

  1. Open the published Template and choose Use to start a Request.
  2. Open Prepare & Send.
  3. Select or right-click the Request Text field and enter the text for this transaction in its Request Text value.
  4. Review the rendered placement and wrapping.
  5. Run Check before Send Now.

In Request mode, QCDS treats an empty Request Text value as a blocking validation problem. The Request cannot be sent until every Request Text field contains the text that will be printed.

What Happens When You Send

At Send Now, QCDS freezes the Request Text value into the immutable Request snapshot as creator-supplied document content. The value is then available to the signer view and completed-document rendering as read-only content.

A later Request started from the same Template begins with its own Request Text value. Changing one Request does not change the Template, another Request, or an already-sent transaction.

Verify the Result

  1. Create two test Requests from the same published Template.
  2. Enter different Request Text values in each.
  3. Confirm each Request shows its own value in the correct PDF location.
  4. Confirm the reusable Template still does not permanently contain either transaction value.

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.