Understanding PrintData and SignData
Understanding PrintData and SignData
Overview
Quik! Forms Engine can return additional generated data with an execute/html response when the related generation properties are enabled.
Two of these objects are especially important in e-signature workflows:
PrintData- contains structured form data and rendering information used for PDF generation and printingSignData- contains e-signature information such as recipient mappings and signing-field/tab information
Understanding the difference between these objects can make it much easier to troubleshoot form-generation and e-signature workflows.
Enabling PrintData and SignData
To request these values from execute/html, include:
{
"GeneratePrintData": true,
"GenerateSignData": true
}
Endpoint:
POST /rest/quikformsengine/qfe/execute/html
Both properties default to false when they are not included.
PrintData
PrintData contains structured field data and metadata used for PDF generation and printing.
Typical uses include:
- carrying form and field data into a later workflow
- generating the document content used for an e-signature envelope
- troubleshooting whether expected form data was generated before the envelope was created
In a Direct to DocuSign workflow, each package supplied to the envelope request has its own printData object.
SignData
SignData contains e-signature field definitions and related signing information.
This can include information for:
- recipients and recipient roles
- signature tabs
- initial tabs
- signed-date tabs
- text tabs
- checkbox tabs
- radio-group tabs
- field locations and page placement
In a Direct to DocuSign workflow, each package supplied to the envelope request has its own signData object.
PrintData vs. SignData
|
Data object |
Primary purpose |
Examples of information |
|---|---|---|
|
|
Represents the generated form/document data used for rendering and printing |
Form IDs, field values, form instances, rendering-related metadata |
|
|
Represents e-signature recipients and signing-field/tab data |
Roles, recipients, signature tabs, initials, dates, checkbox/radio tabs, coordinates |
A useful troubleshooting rule is:
- if the generated document or prefilled values are wrong, inspect the form-generation side first
- if the generated document is correct but signing fields or recipient mappings are wrong, inspect the signing data and downstream e-signature request
How They Fit into Direct to DocuSign
Direct to DocuSign uses a two-call workflow.
Call 1 - Generate the data
POST /rest/quikformsengine/qfe/execute/html
Include:
{
"GeneratePrintData": true,
"GenerateSignData": true
}
The response includes generated data inside ResultData.
A simplified example:
{
"ResultData": {
"UNID": "<generated-unid>",
"HTML": "<generated-output>",
"FormIDs": "<form-ids>",
"PrintData": "{...}",
"SignData": "{...}",
"SignSettings": "{...}"
},
"ErrorCode": 0,
"Message": "Forms generated successfully"
}
PrintData, SignData, and SignSettings are returned as serialized JSON strings in this workflow and must be parsed before they are used as objects in the next request.
Call 2 - Create the envelope
The parsed output from Call 1 is used to build the request to the DocuSign envelope endpoint.
POST https://websvcs.quikforms.com/rest/esignature/docusign/envelope/sign
Each package in packagesData contains its own:
{
"printData": {},
"signData": {}
}
The envelope request also includes signSettings for envelope-level configuration.
See the complete Direct to DocuSign guide for the current request model and transformation example:
Important Distinction - SignData Is Generated Before the Envelope Is Created
SignData is generated by the Forms Engine request before the DocuSign envelope request is sent.
This distinction is useful when troubleshooting.
For example:
- If a signature or radio/checkbox tab is already incorrect in generated
SignData, investigate the form/sign-data generation step. - If generated
SignDatais correct but the final DocuSign envelope is not, investigate the later envelope request and DocuSign behavior.
This helps identify where the workflow first diverges from the expected result.
Do Not Treat Generated Data as a Generic API Schema
PrintData and SignData are generated outputs used by Quik! workflows. When passing them into another Quik! endpoint, use the structure required by that endpoint's current API documentation.
Do not assume that property casing or object structure is identical between:
- the serialized data returned by
execute/html - the parsed data in your application
- the request contract expected by a later endpoint
Use the current Direct to DocuSign documentation and Swagger model when building the next request.
Troubleshooting Checklist
When working with PrintData or SignData, verify:
GeneratePrintDatais set totruewhen PrintData is requiredGenerateSignDatais set totruewhen SignData is required- the expected form IDs were generated
- the expected field values appear in the generated data
- the expected recipient roles appear in signing data
- the expected signing tabs are present
- serialized JSON strings are parsed before being used as objects
- the correct output from Call 1 is passed into the correct package in Call 2

