DocQ Voyager
The May 2022 release marks the debut of DocQ's "Voyager" milestone — a name that reflects the platform's trajectory of continuous growth and expansion. This release delivers four focused improvements that address real-world usage feedback.
JPG Signature Image Support
DocQ's e-signature functionality now accepts JPG images in addition to PNG. This is a small but meaningful quality-of-life improvement. Many users capture their signature images with phone cameras, which default to JPG format. Previously, they needed to convert the image before uploading. Now, both formats work natively.
The broader principle: removing friction from common tasks. Every format conversion, every extra step, every workaround is an opportunity for the platform to do the work instead of the user.
Template Variable Initialization
Templates now support initial value definitions for each variable. When a workflow involves consecutive forms, the initial value from the template carries forward — pre-populating fields automatically.
This is particularly valuable for multi-step processes where the same information appears across several documents:
- Onboarding packages where the employee's name, start date, and department appear on five or more forms
- Contract workflows where company name, effective date, and terms appear on the master agreement, addenda, and signature pages
- Compliance processes where employee ID and department code propagate through acknowledgment, training, and certification forms
Combined with the metadata pre-population feature from the April release, template variable initialization creates a system where data is entered once and flows everywhere it's needed.
Notification Failure Routing
Workflows can now define custom responses when email notifications fail to deliver. Previously, a failed notification was logged but didn't trigger any alternative action. Now, workflow builders can configure rejection routes that activate when delivery fails — for example:
- Routing the task to an alternative approver
- Sending the notification through a different channel
- Flagging the item for manual follow-up
This is important for time-sensitive workflows where a bounced email could silently stall the entire process. Instead of a document sitting in limbo because a notification never arrived, the workflow adapts and keeps moving.
Mobile Interface Optimization
The workflow steps list has been reformatted for mobile devices. On smaller screens, steps now display in a single scrollable column rather than the wider multi-column layout used on desktop.
This matters because workflow approvals increasingly happen on mobile. A manager reviewing and approving a document from their phone should have an experience optimized for that screen size — not a desktop layout squeezed into a smaller viewport.
Continuous Growth
The Voyager milestone isn't an endpoint. Each release builds on the last, expanding what's possible with no-code document automation while keeping the platform accessible to non-technical teams. The features delivered this month — like every month — come directly from how real teams use DocQ in their daily operations.
