Release: The following features and functionalities will go live on June 11, 2026. To learn more about what's included in our June release, refer to What's New in Ironclad: June 2026
Summary
This article describes an upcoming change to how certain Workflow Designer conditions, reset options, and email attachments behave when documents are moved into or out of the signature packet.
Prerequisites
| Features | Workflow Designer, Workflows |
| Permissions | While this update will take place without any action on your part, if you’d like to make any of the changes listed in the FAQs section, you will need Workflow Designer access. |
Who's impacted?
This change may impact you if:
- You use any of the following in Workflow Designer:
- Condition: Draft Document is generated from template
- Condition: Draft Document is not generated from template
- Approval Reset: Draft documents redlined, generated, added, or removed
- Condition: Draft Document is generated from template
- Your workflows do not have a Sign stage (no signers are configured).
What's changing?
“Draft Document” logic will align to “Signature Packet Documents”
"Draft documents" will be sunset and unified under “Signature Packet Documents”. Here's what will change automatically:
-
Conditions that referenced "Draft Documents" now reference "Signature Packet Documents".
- Approval reset configurations that referenced "Draft Documents" now reference "Signature Packet Documents".
- If a document is in the signature packet, it will be considered when these conditions and resets evaluate — regardless of if it was uploaded as an attachment in the launch form or not.
- If a templated or uploaded document is excluded from the signature packet, it will no longer be considered by these conditions/resets.
Default signature packet behavior for certain no-sign workflows
For workflows that do not include a Sign stage (no configured signers), the signature packet can appear empty at the Review stage even when draft documents and attachments exist.
After this update, affected no-sign workflows will have Main Documents that are automatically populated so that it better reflects the documents on the workflow. These documents will be assessed when triggering "signature packet documents" conditions and approval resets.
How will this affect my workflows?
Workflow Designer Conditions
If you have conditions based on draft documents, you may notice that a condition evaluates differently when a document is moved into or out of the signature packet.
Common Scenarios
- A workflow with an attachment in the signature packet will trigger the condition “Signature Packet Documents is not generated from template” to be true.
- A workflow with a templated document moved out of the signature packet at Review will not trigger the condition “Signature Packet Documents is not generated from template” anymore.
Approval Resets
If your configurations resets approvals when draft documents are added, removed, generated in a new version, or edited, changing which documents are in the signature packet will impact when those approvals reset.
Workflows with No Sign Stage
Workflows with no Sign stage behave differently today because the signature packet is typically used for documents that are prepared for signing.
Current Functionality
Currently, at the Review stage, the signature packet can appear empty—even though the workflow has generated documents and/or uploaded files.
Functionality After This Update
- Workflows with no Sign stage will have “Main documents” and “Additional documents” instead of “Signature packet” and “Excluded from signature packet”
- Documents will be in “Main documents” instead of “Excluded from signature packet”
- “Signature packet documents” conditions and resets will consider the documents inside “Main documents”
FAQs
| Question | Answer |
|---|---|
| When is this update being released? | This update will be implemented on June 11th. |
| What is considered a draft document vs. an attachment vs. a signature packet document? |
• Draft Document: Any templated document generated from a template, the main document if a contract is counterparty paper, or a document added to the workflow via “Upload”. • Attachment: Any document uploaded via a file-type question in a Launch Form, Additional Form, or Edit Properties. • Signature Packet Document: Any document currently included in the signature packet. |
| Do I need to do anything right now? |
Most customers won’t need to take action immediately. You do have options to make updates to your configurations:
|
| Will this change impact in-flight workflows? | These changes will affect all workflows (in-flight and net-new). Any Workflow Designer updates you make afterwards will apply to net-new workflows only. |
Resources
Explore articles, courses, and support options to get the most out of Ironclad.
Help Center
- No relevant resources at this time.
Academy
- No relevant resources at this time.