Because you have prefill fields.
If you were to send via the webportaal or used sendocumentinteractive, the sender would have gotten the option to manually prefill those fields, if the sender was not also the first signer. As then they can fill those fields during their signing turn.
Get rid of the prefill roles if you can from the template.
So are you saying that the only way to make this work is to add the sender as the first signer? Is this documented anywhere?
No I'm saying to remove the prefill role from the library document. They have no use in an automated see work flow as the prefill stage doesn't come up for the sender.
If that is true then why does it work when the sender is set as participant1(1st signer)? Is that by design or a bug?
It's by design. The role is called prefill by sender', so when the sender signs first the prefill stage is skipped as it's not needed as the sender can fill these fields when they are signing first.
Prefill is a special sender role which allows senders to fill out fields before sending the agreement. This allows senders to fill these fields prior to sending without needing to be either a signing party in the agreements, or allows them to sign last.
Document Cloud Help | Drag and drop form tool | eSign services see the roles section
Just in case you are merging form data via the AP I; you don't need to assign the prefill role to fields you want to merge into. (using mergefields in the rest method)
You can merge into any valid fieldusing the api regardless of role.
If signers are not expected to interact with fields i recommend not assigning any role to a field, but do set it to read only.
Got it! Very helpful thanks.
Glad it all made sense!