Questions

Hi, I'm receiving the following error in Document Builder when attempting to preview a Word template I am working on:Something went wrongPlease try again later.Contact Adobe Acrobat Sign support if this persists.Error refreshing access token: invalid_request : invalid refresh tokenPer initial research, I found articles suggesting that I need to confirm the installed package version and connect the Adobe Sign account to the Salesforce user. I have confirmed both of these shortly before posting here.In addition, I've scaled down my template to only a few merge fields, saving my Word doc in different file extentions, i.e. .docx vs .doc. I've also confirmed the permissions of my user and the integration user to ensure we have all the permissions possible. I'm at a loss as to what I'm missing. If anyone has any suggestions, I'd be grateful to try.Thank you in advance.

Hello,Is there a way to add a page/file to an existing file in the library template section? When I select the document and click edit I do not see anyway to add another page to my existing and formatted document. I have a contract with all cells set, but I need to add warranty information.

Hello Adobe Support,I am experiencing inconsistent behavior with signature and date form fields when sending documents for e-signature. Below is a detailed description of the issue.1. Word Document Behavior (Working as Expected)When I send a Word document containing the following fields:Signature field ({{Sig1_es_:signer1:signature}}) Date field ({{Date1_es_:signer1:date}})…the behavior is correct:The signature field is editable and functions normally. The date field is automatically populated at the moment of signing. ✔️ Everything works correctly here. 2. PDF Document Behavior (Not Working)When I send a PDF document containing the same field tags, the behavior changes:A. Signature Field as Text → Wrong behaviorIf I send the signature as a text field, the signature is placed in the wrong location (appears in the first empty space on the page, and also Email data is added). The date field is never populated, regardless of field type. B. Signature Field as 'Signature' Type → Correct pla

I have incorrectly typed the same email multiple times when sending documents for signature and now, when i begin typing that same email, 10 of the wrong ones pop up and I need to sort through them to make sure I type the correct email. Is there a way to delete autosaved emails from Adobe Sign so that the correct one autosaves?

I am trying to develop an app and it requires the following scopes:  openid AdobeID user_management_sdk Is there any way other then getting an enterprise account? 

Adobe Acrobat Sign 프로그램을 사용하고 있습니다. 해당 프로그램을 통해 전자 서명을 진행하고 있는데 앱을 통해서 전자 서명을 요청하다보면 좌측 하단에 [탬플릿으로 저장] 하기 버튼이 활성화 되어있는것을 확인할 수 있는데 이렇게 저장된 탬플릿은 어떻게 사용하는 것인가요? 

I am using Adobe Acrobat Sign for our daily cash-out procedure and have created two separate one-page templates to replicate proof sheets from two different financial systems. Each template includes a File Attachment field placed at the bottom of the document so supporting files can be uploaded for that specific proof sheet.On days when activity occurs in only one system, I send a single template without issue. On days when both systems are used, I created a workflow to compile both templates into one agreement so the approver can review and approve everything at once.The issue I am encountering is that all uploaded file attachments are appearing to the very end of the combined agreement, regardless of which template the File Attachment field belongs to. This makes it difficult to determine which attachment corresponds to which proof sheet.My expectation was that each attachment would appear immediately after the document it was uploaded for, since the File Attachment fields are placed

getting error:"The Adobe Sign remote application authorization configured is invalid. Please go to the Adobe Sign Admin page and reauthorize the Adobe Sign application. Contact your Administrator for assistance."Installed in Salesforce, the Adobe account is 'linked', setup successfulUsing Drawloop to send document to Adobe.Error appears when clicking 'Send'Another error: Adobe Sign API returned error: : 401 : {"code":"INVALID_USER","message":"Invalid user ID or email provided in x-api-user header"}Can send document via Adobe , error only in Salesforce

We are putting a workflow in place for new employee contracts and are wondering if there is a way to remove one of the signers from receiving the email with the final signed agreement.  That person gets a lot of emails already and does not want to receive a final copy of every contract.

I’ve spent 3 days looking for a solution, but unfortunately the problem still persists after hundreds of attempts. I paid for a subscription to Adobe Acrobat Pro, which includes e-signing.Here were what I did:sign out and sign in and reboot the system I tried on mobile, ipad, pc, webpage, app cleaned all cookies, history 

I have been an AdobeSign user for 6 years and have lived through all the “improvements.”NOW it has decided that every time I send my rental contract to a guest, who may try to initial and sign it from their smartphone, I must manually tell it to not make the inital field mandatory. So the guest may or may not read that particular page.The fact that Adobesign does not support initialing from a smart phone is absurd.  Please tell me if I am missing something.

Real Time Scenario.

This are my real time scenario so help me.

I open my PDF in Adobe Acrobat Pro, request a signature, add an email address, and click on "Specify Where to Sign", and I get "Authentication Failed".

I created Adobe Acrobat Sign developer account and try to access adobe sign console using "https://secure.adobesign.com/public/login" .After successful login, instead of getting developer console,  I'm automatically redirected to: "https://acrobat.adobe.com/link/home/" instead.How to fix that ?

I have been attempting to use the v6 API to create form fields on a uploaded PDF. Basically, I’m trying to do the v6 REST API version of this: https://helpx.adobe.com/sign/kb/place-form-fields-in-a-document-using-rest-api-adobe-sign.html Is there an update of this or a resource example? It creates the agreement just fine, but no field ever gets created. I have tried many iterations. Here’s the body I was working on in a Logic App: {    "fileInfos": [{        "transientDocumentId": "XXXXXXXXXXXX"    }],    "formFieldGenerators": [{        "formFieldDescription": {            "contentType": "SIGNATURE_BLOCK",            "inputType": "SIGNATURE"        },        "anchorTextInfo":

I complete a form, then select e-signature.  Recipient receives the form blank.  It is removing all completed data from the form.Trying to fix myself, and notice when I go to add the signature recipient in, all the completed data is removed, and new empty text boxes are put in its place.

We have a problem with one of our email addresses that can be recreated by anyone trying to send that user an Adobe document to sign.The issue first surfaced when one of our Directors attempted to get a contract signed by two users.  When we try to enter the problematic user's email address, it gets replaced by Sarah Smith.  The email /Sign document is sent to the correct user so they can sign it.  The issue is under the signature, which shows the correct name; the user name shows Sarah Smith.  As this is a legal document, we need both names to match.Has anyone seen this before? Thanks,Randy

I'm trying to sign up for Adobe E-Sign. after putting my ID and password I just got the following message: "Please accept the Adobe Acrobat Sign invitation previously emailed to you. If you have questions, contact your account administrator."Please let me know for the administrator how to send the Adobe Acrobat Sign invitation again. 

Both accounts used to be part of a Teams account, but are now just on individual Acrobat Pro accounts. 

Im trying to create an agreement via your REST V6 API and everything seems to work, i can upload a document and im receiving a documentTransientId, i can also create an agreement and set some basic data to it. I can also query for views and open those. But every single time im getting an email from adobe which basicly just says “Error during document upload” → we couldnt create your agreement ...See also here:https://helpx.adobe.com/de/sign/kb/adobesign-doc-upload-error.htmlIt really doesnt matter what kind of documents i use, i tried with with an nearly empty .docx-file, i tried multiple pdf files, which only contain texts and were saved as pdf/a. (When opening a document in adobe acrobat it even says so).Do you have any idea what i can do in this case?

PDFs are password protected by default. WHere do I find the password and how to I disable this? Adobe signI'm trying to open a pdf that i exported from my adobe sign account and for some reason, it's password protected. I never set a password for it.Any help?

Is there a way to edit the text once a template has been created?  I am able to edit the fields, but don't see any way to edit the actual text on the document.

We are building an Adobe Sign integration in our application for our customers.We use Adobe Sign REST APIs to create and send agreements with dynamic signature positions provided by our users. To implement this, we followed the approach described in the article below:https://helpx.adobe.com/sign/kb/formfields-option-is-not-available-in-v6-of-rest-api-adobe-sign.htmlCurrent implementation flow: Based on above, we are following below steps in our application now to send agreements.Create the agreement in AUTHORING state using POST /agreement. Get all members (to get participant set IDs) using GET /agreement/{{agreement-id}}/members. Call PUT /agreement/{{agreement-id}}/formFields to update signature positions on the document. If PUT /agreement/{{agreement-id}}/formFields (step # 3) fails, wait for 1 second and then retry step # 3. We repeat this until the call succeeds or the maximum retry limit (5 attempts) is reached. Note: The wait and retry logic was added based on guidance from the

when attempting to send file for e-signature, receiving error message "file upload failed (error code 403):  we were not able to successfully establish any connection with the server."