V2 with Added Features #7
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## Description The rest of the owl
This feature allows signature fields in templates to be automatically signed when a document is created from the template, streamlining the document workflow. Changes: - Added 'autosign' boolean field to the Field model in Prisma schema - Created database migration for the new autosign field - Updated field creation and update functions to handle autosign property - Added UI components to allow users to set autosign option in template field editor - Implemented auto-signing logic in document creation from template - Auto-signed fields are logged in audit trail without IP address - Created SignatureFieldAdvancedSettings component for signature field configuration Technical details: - Autosign fields are automatically marked as inserted during document creation - For signature fields, a typed signature is created with "(Auto-signed)" suffix - Audit logs for auto-signed fields exclude IP address as requested - UI shows autosign checkbox in advanced settings for SIGNATURE and FREE_SIGNATURE field types 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
## Description Add a global flag override for envelopes
This pull request refactors the filtering logic in the `getTeamCounts` function within `get-stats.ts` to improve consistency and maintainability. The main change is the consolidation of multiple filter conditions into a single `AND` clause, which now includes search filters, folder filters, and visibility filters. This ensures that all relevant filters are applied in a unified way for document count queries.
Co-authored-by: Ephraim Atta-Duncan <ephraimduncan68@gmail.com>
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
Currently on inngest the sealing task fails during decoration stating that it can not find the step "xxx" My running theory is that this was due to it being a Promise.all(map(...)) even though that isn't explicitly disallowed. This change turns it into a for loop collecting promises to be awaited after the fact. Local inngest testing looks promising.
Add proper cleanup for PDF.js pages and loading task to prevent memory leaks when processing multiple PDF pages. Ensure page cleanup is called after each page is rendered and both PDF document and loading task are properly destroyed with error handling.
Add fullName prop to signature pad components to automatically populate typed signature field with signer's name. Updates signature dialog, type component, and all signing forms across embed, document, template, and envelope flows to pass through the user's full name for better user experience.
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
…entry (documenso#2328) When flattening PDF forms, some appearance streams lack the required /Subtype /Form dictionary entry needed when used as XObjects. This causes corruption in Adobe Reader which fails to render these flattened fields. Per PDF spec, Form XObject streams require: - /Subtype /Form (required) - /FormType 1 (optional) The normalizeAppearanceStream function ensures these entries exist before adding appearance streams as XObjects to the page content stream. Fixes rendering issues where flattened fields don't display in PDF viewers.
Update main
kevincolten
deleted the
claude/resolve-merge-conflicts-016isSedFvma9SQhZbAfRpx7
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Related Issue
Changes Made
Testing Performed
Checklist
Additional Notes