Skip to main content
TimAck
Participating Frequently
April 10, 2025
Question

New Sign breaks field assignment in existing templates

  • April 10, 2025
  • 1 reply
  • 2543 views

 Long-time user of Sign. Got the notice it's coming, whether we want it or not (and whether it's remotely ready, evidently.) So I tried it out. 

 Documents have, typically, just two signers: me as sender and the recipient. Template docs have assigned fields with assigned fillers/signers/initialers -- either me or the recipient. 
 New Sign breaks the existing templates: now I, as sender, am assigned to initial the various places that the recipient was to do. This is on all of the template documents used, except for the first one selected. Or it might just be that the actual "signature" block on the template that normally is first is not affected, it's hard to pin down.

 Truly a bad way to serve your long-time clients, by breaking the way the entire system is set up. 

 

1 reply

Meenakshi Negi
Community Manager
Community Manager
April 11, 2025

Hi TimAck,

 

Thank you for reaching out.

 

We are sorry, but we do not understand the issue clearly. If you can provide an example of how it used to be and what has changed now, it will help us understand the problem. Once we have the information, we can check this behavior with the team. 

 

We will wait for your response. 

 

Thanks,

Meenakshi

TimAck
TimAckAuthor
Participating Frequently
April 11, 2025

Please see the attached files. The 01/02 files show the two templates and assignment of signers. Those templates are the documents shown in the images labeled 04/05 (they appear both in Sign and "SignNew"). The 03 files show the attached files in both Sign and "SignNew".

When you look at the 05 file for Sign, it properly assigns the initials on the top of Exhibit A to TEST2, the person to whom I am sending the agreement. When you look at the 05 file for SignNew, it assigns those initials to me instead. 

Meenakshi Negi
Community Manager
Community Manager
June 13, 2025

I evidently got forced into the new version and it's broken again. That is aside from the many other issues that others have pointed out elsewhere (e.g. it repeatedly crashes, claims its out of memory (when Task Manager plainly reveals that not to be true at a system level), is excruciatingly slow to load files, etc., etc.).

I am using "Request e-signatures" from "All tools" on https://acrobat.adobe.com/link/tools/ (which seems to be the same as this link elsewhere on the page: https://acrobat.adobe.com/link/acrobat/sendforsignature/?locale=en-US). 

It is again causing the problem where previously acceptable / functional documents now are processed in such a way that I described above: I, as first signer, am now assigned all the "initial here's" throughout the document, when those were formerly processed for the second signer. 

Please let me know how to upload documents that are not available to the public at large. 


Hi TimAck,

 

We are sorry to hear about your experience. 

Could you please share more information about the workflow that is not working as it used to? A video will be helpful so we can discuss it with the team.

 

Thanks,

Meenakshi