93a3809f6a
fix: add maxLength limits to document input fields ( #1988 )
2025-09-09 17:52:03 +10:00
bb5c2edefd
feat: implement auto-save functionality for signers in document edit form ( #1792 )
2025-09-02 21:01:16 +10:00
3409aae411
feat: add email domains ( #1895 )
...
Implemented Email Domains which allows Platform/Enterprise customers to
send emails to recipients using their custom emails.
2025-07-24 16:05:00 +10:00
e6dc237ad2
feat: add organisations ( #1820 )
2025-06-10 11:49:52 +10:00
55c8632620
feat: password reauthentication for documents and recipients ( #1827 )
...
Adds password reauthentication to our existing reauth providers,
additionally swaps from an exclusive provider to an inclusive type where
multiple methods can be selected to offer a this or that experience.
2025-06-07 00:27:19 +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
063fd32f18
feat: add signature configurations ( #1710 )
...
Add ability to enable or disable allowed signature types:
- Drawn
- Typed
- Uploaded
**Tabbed style signature dialog**
**Document settings**
**Team preferences**
- Add multiselect to select allowed signatures in document and templates
settings tab
- Add multiselect to select allowed signatures in teams preferences
- Removed "Enable typed signatures" from document/template edit page
- Refactored signature pad to use tabs instead of an all in one
signature pad
Added E2E tests to check settings are applied correctly for documents
and templates
2025-03-24 17:13:11 +11:00
383b5f78f0
feat: migrate nextjs to rr7
2025-02-13 14:10:38 +11:00
9e03747e43
feat: add create document beta endpoint ( #1584 )
2025-01-16 13:36:00 +11:00
6fc5e565d0
fix: add document visibility to template ( #1566 )
...
Adds the visibility property to templates
2025-01-09 10:14:24 +11:00
487f52e194
feat: enable optional fields ( #1470 )
2024-12-27 19:30:44 +11:00
f6bcf921d5
feat: add document distribution setting ( #1437 )
...
Add a document distribution setting which will allow us to further
configure how recipients currently receive documents.
2024-11-08 13:32:13 +09:00
4dd95016b1
feat: i18n for emails ( #1442 )
...
## Description
Support setting a document language that will control the language used
for sending emails to recipients. Additional work has been done to
convert all emails to using our i18n implementation so we can later add
controls for sending other kinds of emails in a users target language.
## Related Issue
N/A
## Changes Made
- Added `<Trans>` and `msg` macros to emails
- Introduced a new `renderEmailWithI18N` utility in the lib package
- Updated all emails to use the `<Tailwind>` component at the top level
due to rendering constraints
- Updated the `i18n.server.tsx` file to not use a top level await
## Testing Performed
- Configured document language and verified emails were sent in the
expected language
- Created a document from a template and verified that the templates
language was transferred to the document
2024-11-05 11:52:54 +11:00
28514ba2e7
fix: duplicate templates ( #1434 )
2024-11-01 21:29:38 +11:00
75c8772a02
feat: web i18n ( #1286 )
2024-08-27 20:34:39 +09:00
7b5c57e8af
chore: add more field types ( #1141 )
...
Adds a number of new field types and capabilities to existing fields.
A massive change with far too many moving pieces to document in a single commit.
2024-07-18 23:45:44 +10:00
c3035dbd15
feat: add external id to documents and templates ( #1227 )
...
## Description
Adds the external ID column to documents and templates with an option to
configure it in the API or UI.
External ID's can be used to link a document or template to an external
system and identify them via webhooks, etc.
2024-07-13 16:45:09 +10:00
2f86bb523b
feat: add template enhancements ( #1154 )
...
## Description
General enhancements for templates.
## Changes Made
Added the following changes to the template flow:
- Allow adding document meta settings
- Allow adding email settings
- Allow adding document access & action authentication
- Allow adding recipient action authentication
- Save the state between template steps similar to how it works for
documents
Other changes:
- Extract common fields between document and template flows
- Remove the title field from "Use template" since we now have it as
part of the template flow
- Add new API endpoint for generating templates
## Testing Performed
Added E2E tests for templates and creating documents from templates
2024-05-10 19:45:19 +07:00
