Designer view implementation in both ways
Wednesday, July 29, 2020 at 09:00amHello Support,
We are using .NET sdk for designer view.
but, when user implementing designing view, every time he has to place signature on document and send e-sign email.
so, my question is that do you have any method that supporting e-signing both ways in designer view?
1. Do we add signature in fixed location. so, user don't need to drag and drop signatures on document every time.
2. Also, if he want to add signatures on the fly. he can do without any restriction.
Thanks in advance.
Reply to: Designer view implementation in both ways
Wednesday, July 29, 2020 at 09:31amHi there,
Actually the designer view can be used in a very flexible way - you can remove the "send" button in the designer page and use a custom button in your application as a more unified way to send the package. So that designer view doesn't have to be the last step of the designing flow, package sender can open designer at any time, the signatures can be fully or partially added by SDK code, and sender only opens the designer page when it's necessary.
For your reference, I have a blog series covering everything you need to know about designer view:
https://www.onespan.com/blog/onespan-sign-developer-designer-customization-and-integration-part-1
https://www.onespan.com/blog/onespan-sign-developer-designer-customization-and-integration-part-2
https://www.onespan.com/blog/onespan-sign-developer-designer-customization-and-integration-part-3
https://www.onespan.com/blog/onespan-sign-developer-designer-customization-and-integration-part-4
https://www.onespan.com/blog/onespan-sign-developer-designer-customization-and-integration-part-5
Where in the part 3 & 4, I have two demos showcasing how you can involve the designer view in your flow.
Duo