-
Notifications
You must be signed in to change notification settings - Fork 464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] default values for text fields #119
Comments
@fotofiete there are two ways to improve this workflow:
- You can try to add yourself as the first submitter of the form - you'll
fill the event name and date for them, and once it's done the form will be
passed to them with those fields already filled and displayed in the form
where they just need to put their signature.
- You can create a new PDF with those fields already pre-filled - and then
you can just replace the existing document file in the cloned template form
- all fields should remain in their place and you don't need to redraw them
(replace button appears if you hover on the page preview on the left)
Let me know if anything from the above solves your problem
…On Wed, Oct 11, 2023 at 5:35 PM Fiete ***@***.***> wrote:
Hi,
we really like working with docuseal in our org! One use case we have is
to sign a photo declaration for events. Therefore we have a blueprint with
fields for the events name, the date, the name and the signature.
When starting a new event we clone this blueprint and invite all the
events guests. This has the downside, that the user has to fill in event
and date on his own which might lead to heaps of different values. Here it
would be great to be able to either add a standard text (without a form
field) holding e.g. the events name or to be able to provide a default
value for a text field...
Other possibility of course is to create a new form with a new PDF holding
these values but then you have to recreate all the other input fields...
(Or do I missunderstand something basically? 🙈 )
Thanks for your work! 😄
—
Reply to this email directly, view it on GitHub
<#119>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAI7GLZRD36ND6YZI6BTYUTX62VC3ANCNFSM6AAAAAA54DRUAM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
@AlexandrToorchyn ah cool, thanks for your reply – especially the way to exchange the PDF file sounds very promising! :) for me that's fine as a solution – it's up to you to leave this ticket open to still implement a possibility for read-only fields or default values (which both would be cool, too!) or to close it as resolved... 😄 |
@fotofiete default values have been added in the 1.2.6 version: |
Hi,
we really like working with docuseal in our org! One use case we have is to sign a photo declaration for events. Therefore we have a blueprint with fields for the events name, the date, the name and the signature.
When starting a new event we clone this blueprint and invite all the events guests. This has the downside, that the user has to fill in event and date on his own which might lead to heaps of different values. Here it would be great to be able to either add a standard text (without a form field) holding e.g. the events name or to be able to provide a default value for a text field...
Other possibility of course is to create a new form with a new PDF holding these values but then you have to recreate all the other input fields...
(Or do I missunderstand something basically? 🙈 )
Thanks for your work! 😄
The text was updated successfully, but these errors were encountered: