d05bfa9fed
feat: add envelopes api ( #2105 )
2025-11-07 14:17:52 +11:00
7f09ba72f4
feat: add envelopes ( #2025 )
...
This PR is handles the changes required to support envelopes. The new
envelope editor/signing page will be hidden during release.
The core changes here is to migrate the documents and templates model to
a centralized envelopes model.
Even though Documents and Templates are removed, from the user
perspective they will still exist as we remap envelopes to documents and
templates.
2025-10-14 21:56:36 +11:00
4012022f55
fix: element visible race condition ( #1996 )
...
On larger documents we could accidentally start trying to render fields
while not all pages of the PDF have loaded due to us checking for a
single page existing. This would cause an error to be thrown, hard
locking those documents.
This change resolves this by grabbing the highest page number from the
given fields and using it for the visibility check instead.
2025-08-26 11:08:43 +10:00
99b0ad574e
feat: bulk add fields ( #1683 )
...
## Demo
---------
Co-authored-by: Lucas Smith <me@lucasjamessmith.me >
2025-05-14 19:35:32 +00:00
12ada567f5
feat: embed authoring part two ( #1768 )
2025-05-01 23:32:56 +10:00
193325717d
fix: rework fields ( #1697 )
...
Rework:
- Field styling to improve visibility
- Field insertions, better alignment, centering and overflows
## Changes
General changes:
- Set default text alignment to left if no meta found
- Reduce borders and rings around fields to allow smaller fields
- Removed lots of redundant duplicated code surrounding field rendering
- Make fields more consistent across viewing, editing and signing
- Add more transparency to fields to allow users to see under fields
- No more optional/required/etc colors when signing, required fields
will be highlighted as orange when form is "validating"
Highlighted internal changes:
- Utilize native PDF fields to insert text, instead of drawing text
- Change font auto scaling to only apply to when the height overflows
AND no custom font is set
⚠️ Multiline changes:
Multi line is enabled for a field under these conditions
1. Field content exceeds field width
2. Field includes a new line
3. Field type is TEXT
## [BEFORE] Field UI Signing
## [AFTER] Field UI Signing
## [BEFORE] Signing a checkbox
## [AFTER] Signing a checkbox
## [BEFORE] What a 2nd recipient sees once someone else signed a
document
## [AFTER] What a 2nd recipient sees once someone else signed a document
## **[BEFORE]** Inserting fields
## **[AFTER]** Inserting fields
## Overflows, multilines and field alignments testing
Debugging borders:
- Red border = The original field placement without any modifications
- Blue border = The available space to overflow
### Single line overflows and field alignments
This is left aligned fields, overflow will always go to the end of the
page and will not wrap
This is center aligned fields, the max width is the closest edge to the
page * 2
This is right aligned text, the width will extend all the way to the
left hand side of the page
### Multiline line overflows and field alignments
These are text fields that can be overflowed
Another example of left aligned text overflows with more text
2025-04-23 21:40:42 +10:00
e613e0e347
feat: support embedded authoring for creation ( #1741 )
...
Adds support for creating documents and templates
using our embed components.
Support is super primitive at the moment and is being polished.
2025-04-11 00:20:39 +10:00
