Conditional visibility simplifies forms and reduces signer confusion by dynamically presenting only necessary fields based on answers or context.
Form Authors design the PDF and set conditional rules. They map field names, create logical expressions, test visibility across scenarios, and document rule rationale so administrators can maintain the form without introducing conflicts.
Signers encounter the conditional fields on-screen; their inputs trigger visibility rules. They see a simplified, context-appropriate form and rely on clear labels and validation to complete required entries accurately.
Organizations and form authors use conditional visibility to tailor forms by role, workflow, and input values.
Proper role mapping, testing, and audit logging help these users maintain compliance and reduce data entry errors across workflows.
Drag-and-drop or form-based editors let authors build conditional logic without writing code, supporting comparisons, boolean operators, and nested conditions with readable labels for maintainability.
Preview allows switching signer roles and sample data to validate field visibility across multiple scenarios before publishing to production to reduce runtime errors.
APIs enable passing external values to forms at runtime and triggering rule re-evaluation, supporting CRM-driven prepopulation and conditional flows for integrated systems.
Version control and change history track rule updates, so administrators can audit changes and roll back to earlier configurations if a rule introduces unintended behavior.
| Feature Configuration and Default Values | Default configuration values and brief descriptions |
|---|---|
| Field Visibility Rule Engine | Expression-based engine |
| Rule Evaluation Trigger Event | On field change or load |
| Default Visibility State | Hidden unless condition met |
| Validation Behavior for Hidden Fields | Skip validation when hidden |
| Audit Logging Level | Full event-level logging |
Confirm platform support for dynamic rendering and rule evaluation across desktop, browser, and native mobile apps before deployment.
Test conditional behavior in each supported signing channel, validate how viewers cache or pre-render pages, and document any platform-specific limitations to ensure consistent signer experiences and accurate data capture.
A patient intake PDF shows additional insurance fields only if the patient selects that they have coverage.
Resulting in fewer manual follow-ups and clearer patient records.
An order PDF reveals warranty and shipping options when high-value products are selected.
Resulting in faster order processing and fewer post-order corrections.
| Criteria for Feature Comparison Table | signNow (Recommended) | DocuSign | Adobe Sign |
|---|---|---|---|
| Support for conditional form field visibility | |||
| Server-side rule evaluation availability | Limited | ||
| Mobile viewer conditional rendering consistency | High | High | Medium |
| API support for runtime field injection | REST API | REST API | REST API |
If you need to send a package of documents for eSignature or review to different recipients in multiple consecutive steps, create a Document Group and set specific conditions for automatic document routing. This feature allows you to build advanced document workflows in a very straightforward way.
Let’s say you are an HR manager and you need to send several onboarding documents to a new employee and your company’s CEO for approval. Once the documents are signed by both parties, you need them forwarded to the accounting department and also back to you. Let’s build this workflow with airSlate SignNow to see how easy it is.
Hover over the Upload or Create button and select Create Document Group.
Upload documents that need to be sent from your hard drive or add them from your Documents or Templates folder on airSlate SignNow. For this example, we’ll choose the latter option.
Select the documents you need from the list and click Add.
The files we’ve added to this Document Group already have fillable fields and signing roles configured (CEO and New Employee). You can make changes to any of your documents by clicking the Edit Document button. When finished, click Next.
Configure your first signing step. In our case, we need to send an employment contract, NDA, and company policy to a new employee for eSignature.
Enter your recipient’s email address and click Assign Documents and Roles. Then, select the documents you need to send and click Apply.
Choose a signing role for each document using the corresponding dropdowns. For this step, we’ll assign the New Employee role.
Let’s set up the second step by clicking the Add Signing Step button. Once the documents are signed by the new employee, we need them to be approved by the company CEO. So we configure the next step in a similar fashion but assign the documents to the CEO.
Now it’s time to configure the third and final step. In the end, we need airSlate SignNow to forward all these signed documents to the accounting department and HR.
First, add the accountant’s email address, and then, by clicking the Add recipient button, add the HR to this step (both recipients will receive the document package simultaneously). We don’t need the accountant and HR to sign these documents, so we choose View only in the dropdowns (you don’t need signing roles for this option).
When finished, click Next.
Everything is set and ready to go. All you need to do is review your signing steps and hit Send. You can also customize your email subject and message for each step, set up signer authentication, and schedule reminders by clicking Customize Email Settings.
Once your Document Group is sent, the workflow is set in motion and your documents will be automatically routed to the designated recipients.
