We are using Rest API V2 that we use a c# Winform application. We create an envelope with a document in it using the api. We then redirect user to a win form with a browser control (Internet Explorer). It worked without issue until late august and we had problems with some users getting logged out after 20-40 seconds while trying to add tags and templates. It started out with a few users having the issue and seems to be happening more often.
Additional Info.
It doesn't seem to matter on size of document / what you are doing . It happens if you are doing nothing or dragging and tagging etc. It seems to only happen on the preview screen that you can do the drag/tag. This is a sampe of the URL it times out to docusign.com/… – user3022205 Nov 26 at 18:57
Related
The problem is that in Manage Clients at https://www.instagram.com/developer/clients/manage/ client was created,
but it became invalid, the id did not work, i.e. instagram disabled it, the inscription was disabled.
We decided to delete the old client and create a new One, but instagram does not register it. The line of consent and the captcha does not issue. Respectively writes 2 errors:
1.Incorrect Captcha. Try again.
2.Error sending: fill in all required fields.
How can this be corrected?
I've had this same issue, and haven't been able to get anywhere with it. The support page for Instagram says to report a bug using the "Report Bug" button on the Developer Dashboard (http://instagram.com/developer/clients/manage/). If you click that button it takes you to a form that asks if you want to report a bug for the old API or new API. If you select the old API it says "we're not taking bug reports for the old API", if you select new API it takes you to Facebook's developer support page. I created a ticket there, and they told me I had to report it through Instagram's support links. WTF?? That's what I did .....
Anyways, the problem is related to a bunch of javascript errors on that client registration page. I first encountered this problem about 3-4 weeks ago, and it's still around. Feels like IG really doesn't give a crap about their developer community ....
We are using docusign for more than 3 years, We have several demo accounts as well as we have paid account too.
we are using the following docusign rest service
https://demo.docusign.net/restapi/v2/accounts/*****/envelopes
In our local environment we are using the above demo rest service, Till last month (August) we were able to post the document into docusign without any issues. The Problem now is that we are not able to post a document to docusign.
we getting the exception like
"errorCode": "UNABLE_TO_LOAD_DOCUMENT", "message": "Unable to load the document. Unable to load Document(1;CONSENT FORM). Error: Cannot add the widget (connected to field: ColombiaCurrentlyresideYes) to page -1, because it's already added to page -1. If you want to re-use this widget, please remove it from the current page first
Same data worked till last month (August) and it's working fine now in docusign production account(paid). we are not sure what went wrong in demo accounts. Any release are done in demo accounts?
I tired using the same template in web console too, same error throws in browser console
Please help me to resolve this issues.
We require your guidance regarding this issue!
I suggest first trying to load the documents into an envelope by using the DocuSign Web tool (NDSE). If that doesn't work then the document is the issue.
Has the document changed?
Re changes: Yes, the demo system is changed each month. Then the changes are applied to the production systems. While we do have thousands of automatic regression tests, problem can creep through the system.
I suggest you contact DocuSign customer support to give them the document which is failing to load.
This is complicated but I'll try to explain. I've written an API integration in PHP. With this module installed on my website, I'm able to call a web service (on my website), pass it a PDF, and a collection of requisite parameters including a specific template ID in my Docusign account, and get back an embedded signing link, which I can then use to redirect to the Docusign signing experience for that template/document combination.
The PDF document I'm passing is the exact same PDF in the selected template, but with data filled into some of the files, whereas the version in the template is blank. In the template, various fields are defined (signature tab, date signed, SSN, etc..). These are clearly visible and correctly configured. One can verify this by going into the account and editing the template in question from the Docusign web UI.
My problem is that of the 5 templates I have configured, only one is working as expected (PDF shows up, you fill in the fields and sign, and click "Finish"... callback web hook fires delivering the finished PDF back to my server... done.). The rest show none of the configured fields signers are supposed to interact with. You can click continue, but in the left sidebar, you get the tools for adding fields to the document, instead of the pre-configured ones displaying properly in the body of the PDF.
The template that's working, was broken two days ago with the symptoms described above. I've done nothing to the account or that template and it's magically working somehow. I called tech support on Friday and they told me that occasionally templates get corrupted on the docusign server, but that was tier 1 support and I'm not sure that's a valid comment.
That's about the best I can do to describe the problem. I'm unsure what specific information I could supply to help troubleshoot this, but I'll watch the thread and react as quickly as possible.
I'm observing the exact same behavior in both dev and live environments with the exact same group of templates. The one that works in the live environment is the same one that works in dev.
List of templates: (this is for the Dev implementation)
86841739-f12d-460e-9807-23a9b90cff6b (only this one works)
6c3fd328-6f2e-4de1-a9bc-f50df7761ec2
68ce0c9e-a892-4a15-b0f5-39f28aba4588
cd4e3b6d-a8ea-4c78-a0f8-602753996743
9278c78b-f703-429a-ac62-9361bd02f54a
The above represents the 5 templates I'm testing. Only the first one works as expected. I'll add the json later this evening, as I'm out of time at the moment.
Here's the json for each of the templates (zip file):
https://ufile.io/quo3j
Problem solved. It was indeed a discrepancy between the roleName of the template and that passed to the API during envelope creation. They must be the same. If you use a template with a different roleName than the one you pass when creating an envelope, you will get the exact behavior I've described.
The solution is to edit your templates on the Docusign website, and use the same roleName for them all, then make sure that's what you're passing the API when creating envelopes.
All I want to do is show the most recent of our client's Instagram posts on the website we are building for them.
This was possible using only their ClientID until November 2015, but Instagram seem to have made it so that we have to get users to log in so we can get an access token to use in the API call.
This seems nonsense and I can't help feeling I'm missing something simple. I should be able to display client's content on their website without viewers of the site having to log into Instagram!
There are a number of solutions on Stack Overflow, but all the ones I've found pre-date Nov. 2015.
Use your own access_token.
Get it one time, save it and use it, it is not eternal though. I have the same problem.
I am working on an Outlook mail app, which will be available to user on web only (not of outlook desktop).
A file need to be uploaded from app to azure via custom control in compose form of App, meanwhile the file is uploaded to Azure user should not be able to close the mail. If they try to do so, a warning should be given to them.
Adding to #Slava's answer, I would suggest using addAsync API for notification messages. You can add a notification of type progress indicator until your task is complete and replace it with a notification of type informational message.
Click here for reference
Unfortunately Office.js API does not have the feature you are inquiring. You will not be able to disallow user interaction, as such closing the compose window or closing your add-in. As the API doesn't have "OnSend" or "OnClose" events you will not be able to display any warning either. If this is the new feature you would like to add you may try to send request via Office Developers User Voice.
As the work around you should clearly indicate for the users that they need to wait and do not interup operation. You should display activity indicator, indeed. And finally you should be prepare user still interupt the operation in the middle and work properly with the error occur.
Hope this helps.