Signature fields indeed need the assignee property to be used. Regular fields don't need to be assigned. You need the participantSetID which you can get by calling GET/agreements /{agreementId} /members A successful PUT call moves the agreement to IN_PROGRESS, no need to call the state end point.   ... View more

the syntax for the the 'In the name of' is indeed: 'email:myemail@email.com' (without quotes). The email address bus be the owner of the agreement, in other words the sender. You can add that as a dynamic value from a get document status action.   the sender needs to also be a user in the same Sign account as the user who has authroised the Sign connector.  Alternatively ensure the Sign connector is authorised by the same user who has send the agreement.     ... View more

60 days, see https://secure.eu1.adobesign.com/public/static/oauthDoc.jsp ... View more

specific signers only appear when editing an agreement as part of sending an agreement. When editing a template we have placeholder i nthe form of participant 1, participant 2 etc. If you need more palceholders they can be added via the top right  more info on working with templates https://helpx.adobe.com/uk/sign/using/create-document-template.html ... View more

Sign does not really allow to hide page as such. However who is filling out the fields on page 1? Is it the person who initiates the process, or the person who signs it?   With Sign, if you have the data already on page 1, the sender/initiator can prefill this data and merge it into the main document. ... View more

A Dev account is meants to be used for testin, which is why you see watermarks and the adding of the Demo text into the name of the agreement. Paid for Sign production entperise accounts can be used with the Sign api as well. ... View more

I did forget the ldv requirement. In any case to save some transactions you can register for a free Dev account. It has the functionality of a normal account, but does use watermarks on all output: https://www.adobe.com/sign/developer-form.html use a gmail or yahoo or other public email to register.   Indeed with LDV in mind and creating the seperate templates, you can't create the formula on the page without some sort of reference to the original 'masterfield' on each individual template. So 3 options 1: Forget about being clever and have individual fields (possibly each field pre-populated from the workflow 2: have a placeholder/master field in each template. The placeholder version can be disuised by making them tiny.  3: text tagging is another way in theory, but may become a too complex solution compared to 1 and 2.         ... View more

the Post request to get the access token cannot be done with url parameters, see https://secure.eu1.echosign.com/public/static/oauthDoc.jsp also you need to call the api endpoint https://api.eu1.echosign.com  (adjust for your region/shard if needed) ... View more

No, timestamping is currently only done when signing using a digital certificate.   ... View more

One thing to consider is that for for the quote the participant is set to an Approver role, or Acceptor role instead of the default Signer role. This changes the verbiage in the emails a bit.   This setting cannot be set per template, but can be set on a group level. if users in multiple groups is enabled then you can assign the sender to 2 groups. One for the quote and one for the order form. Se the quote group to not include attachments and the order form to include them.   On the send page select the group required for each tempalte or do this via a Sign workflow.   A more advanced option is to use the API where you can control this on the agreement level. ... View more

Adobe Sign combines multiple documents into a single document. So when 2 files/templates have a field with the same name they become duplicate fields. To stop this you need to provide unique names on each of the template if they can be combined together. You can use a simple numbering system If you have 5 docs and a Name field which should be treated as a unique field in the combine document name the fields something like so   'Name-doc1' in Doc 1 template and 'Name-doc2' in Doc 2 tempalte and so on ... View more

you can create form field layer templates https://helpx.adobe.com/sign/using/create-document-template.html ... View more

Webform are your best bet and option requires developer resources and or acces to MS 365 licensing to access MS power automate.   Webforms in Sign do require a small business account or better: https://www.adobe.com/uk/sign/pricing/compare-plans.html ... View more

If you login the Sign webportal and go to the manage tab, go to these agreements and send reminders to the current participants for the agreement and see if they get this email.     ... View more

If Sign is prefilling your signature appearance then it means you have an active registered Sign user account. You can browse to  https://secure.adobesign.com/public/login   enter your email address as the username  and tab to the password field. The page should redirect to an AdobeID login, so login using your AdobeID. Then in the upper right corner fina your username and click that ad select profile. On the left hand see if you can see 'My Signature' and select that.   Here you can set your signature appearance or indeed clear it. ... View more

Well this is indeed a curious case from what i can see. One thing is for sure, you won't fix it be re-installing Acrobat. I assume Judy is using Adobe sign via Acrobat's 'request Signature?'   if so, ask her to login directly into Adobe Sign (so not via Acrobat) using the url below   https://secure.na2.adobesign.com/public/login This will bring up an Adobe Sign login page, enter the email address and tab to the password field The page shoul redirect to a general Adobe login screen. if prompted to select between adobe ID and and Enteprise, Judy should opt for Entperise and login using SSO.   If the login is succesful, Judy can try and send an agreement from the send page instead and let us know which email address that comes from.   If it still comes from Jennifer's email, then your Adobe admin should reach out to either support or your Adobe CSM for assitance, as there may well be an issue with Judy's Sign user (not her Adobe user, there is a difference). ... View more

The defaul is to only have the email itsefl as authentication. If you are unable to change this option (try clicking the arrow near the mobile phone icon), your group or account admin has made this the required default. They would need to change this requirement for you,   ... View more

With Adobe Sign, you either use the Adobe Sign authentication, or the OTP authentication for a given participant. You can use both at in the saem agreement for the same participant.   Now Adobe Sign auth means that the signer needs to have an Adobe Sign account. Therefore this method works best when the sender is sending the agreement to signer who are in the same Adobe Sign account as the sender (aka internal signers)   For external signers the sender may not know if the signer has an Adobe Sign account, so it's better to use the OTP option.   As said the Adobe Sign login is governed by the overall SSO setting for that Sign account. If the SSO is configured to do a Phone OTP, then that's something that is controlled in the SSO Id provider. (though I've not heard of OTP being used for SSO, more common SSO is to login in compnaycertificates/smart cards)   Wether that's overkill or not will depending on your company policies and/or GXP./cfr21 audit person. Also this article and link to Montrium Sign validaiton pack for cfr21 compliance may be useful if you haven't seen it already: https://helpx.adobe.com/uk/sign/using/21-cfr-validation-pack.html ... View more

To create a recipient group, add a member to to to relevant participantset memberinfo array.   "participantSetsInfo": [ { "memberInfos": [ { "email": "myexample1@example.com" } ], "order": 1, "role": "SIGNER" }, { "memberInfos": [ { "email": "myexample2@example.com" } ], "order": 2, "role": "SIGNER" }, { "memberInfos": [ { "email": "myexample3A@example.com" }, { "email": "myexample3B@example.com" } ], "order": 2, "role": "APPROVER", "name": "a recipient group" }, { "memberInfos": [ { "email": "myexample4@example.com" } ], "order": 3, "role": "SIGNER" } ]   Members of a recipient group receive the agreement at the same time, but only one mmeber has to sign in order to move teh agreement to the next step ... View more

3 to have a hybrid of sequential and parallel adjust the signing order: "participantSetsInfo": [ { "memberInfos": [ { "email": "myexample1@example.com" } ], "order": 1, "role": "SIGNER" }, { "memberInfos": [ { "email": "myexample2@example.com" } ], "order": 2, "role": "SIGNER" }, { "memberInfos": [ { "email": "myexample3@example.com" } ], "order": 2, "role": "APPROVER" }, { "memberInfos": [ { "email": "myexample4@example.com" } ], "order": 3, "role": "SIGNER" } ] So in the above, the agreement goes to the first set, then they sign, it goes to the 2 sets with signing order 2, then these 2 sign and approver the agreement is sent to the final participant (example4@example.com) ... View more

For the parallel workflow, simply set all sets to the same signing order: "participantSetsInfo": [ { "memberInfos": [ { "email": "myexample1@example.com" } ], "order": 1, "role": "SIGNER" }, { "memberInfos": [ { "email": "myexample2@example.com" } ], "order": 1, "role": "SIGNER" }, { "memberInfos": [ { "email": "myexample3@example.com" } ], "order": 1, "role": "APPROVER" }, { "memberInfos": [ { "email": "myexample4@example.com" } ], "order": 1, "role": "SIGNER" } ] ... View more

The sequential order explained above can be done as below. (i have simplified the json to the minim needed: "participantSetsInfo": [ { "memberInfos": [ { "email": "myexample1@example.com" } ], "order": 1, "role": "SIGNER" }, { "memberInfos": [ { "email": "myexample2@example.com" } ], "order": 2, "role": "SIGNER" }, { "memberInfos": [ { "email": "myexample3@example.com" } ], "order": 3, "role": "APPROVER" }, { "memberInfos": [ { "email": "myexample4@example.com" } ], "order": 4, "role": "SIGNER" } ] ... View more

Considering the webportal Send page use the same API call, it's yes you can use the API to achieve the same result. 🙂   Here's the json covering the participantsetinfo: "participantSetsInfo": [ { "memberInfos": [ { "email": "", "id": "", "securityOption": { "authenticationMethod": "", "nameInfo": { "firstName": "", "lastName": "" }, "notaryAuthentication": "", "password": "", "phoneInfo": { "countryCode": "", "countryIsoCode": "", "phone": "" } } } ], "order": 1, "role": "", "id": "", "label": "", "name": "", "privateMessage": "", "visiblePages": [ "" ] } ] The participantSetsInfo is an array in which you can have multiple sets. Within each set you have a memberinfos array, where in most case you have a single member, but if using recipient groups this can have multiple members. ... View more

Acro Forms and Sign form are 2 different beasts. Sign forms have no support for any kind of JS, which is what is needed to support things like a calendar pop-up in Acrobat.   In Sign either signers enter a date into a text field, though the text field can be set to validate only for date formats. In acrobat name the field like so MyDate_es_:signer1:isdate(format=dd/mm/yyyy)   Sign will turn that into a text field called Mydate and assign it to th first participant and with a date validation in the dd/mm/yyyy format)    Sign also has field to populate the current date in which case name your Acro field Today_es_:signer1:date   This is an auto date which will be formatted per Sign account setting. ... View more

Can you clarify your query, I'm not sure what you are asking. For CFR21 purpose, the rules require a signer to be authenticated before viewing the agreement/signing and also when the signature is applied. Sign supports 2 types of authentication, -Adobe Sign auth and - Phone One time Pin auth.   The former will ask a Signer to login their Sign account before and after, and the method of login is determined by that Signers Sign account. If that Sign account is configured for SSO, then which ever system and rules of SSO will be used for that Signer. ... View more

Are you using Adobe Sign via the adobe Sign webportal? In which case you can use the X next to the email to get rid of it: If using Sign through Acrobat, then you'll need to dive into the registry and modiy/delete the following key HKEY_CURRENT_USER\SOFTWARE\Adobe\Adobe Acrobat\DC\Workflows\cServices\cSendForSignature\cUser\taddressList   If using Reader, replace Acrobat with Acrobat Reader in the above path. ... View more