I am calling createRecipientView and using the response to generate an iFrame in my application. However, it appears that viewing this iFrame only works one time - subsequent views of the iFrame send the user to the returnUrl.
This is a problem because in my application we maintain documents that the user can sign at their convenience - so they may look at the document and decide to sign it later... which means that we will need to call createRecipientView again and get a new URL for the iFrame.
Am I understanding this correctly? I can't find much documentation on the URL returned - does it only expire once viewed, or does it expire after a certain amount of time / other conditions?
You are correct; the URL will expire either after being used, or after five minutes (token TTL of 300 seconds).
Please note that an iFrame is not a good idea. Especially if your app will ever be used from a mobile or tablet browser.
I have updated the docs for the EnvelopeViews: createRecipient method with information about the one time/limited time use of the URL.
Related
Observed the Integration APIs (Token Creation, Envelope Creation, Receipient View Creation) itself taking ~5-6seconds & the rest of the time in loading the docusign page in iframe.
This may be normal, it depends on the amount of data (size of documents) and how busy DocuSign servers are.
You don't have to block the UI right away, when you create the envelope and make the next API call, you can have the UI ready, do this in the background and prepare everything and then show it to the user. This way you avoid the 10 seconds delay that, I agree, is not an ideal user experience.
Issue 1 - Now I am using Code Grant and fetched token with refresh token, still it is not working, next day when I am using same token generated with refresh_token is giving error
Issue 2- How can I get uri or path of that file - so that user can click that link - view status - download ?
like https://demo.docussing.com/accountid/envelopeid/documentid some thing like this, once user click on that page it will open that page showing current state of document
StackOverflow is best used as one-topic-per-question. When asking, it's best to provide as much detail as possible about what you're doing, what's wrong, what errors are received, and what you've tried to do to investigate.
For issue 1, access tokens last for eight hours, so when an access token expires you will need to generate a new one. Based on your question, I'm not sure that's happening - Are you able to use the refresh token to generate new access token, or is that what's failing?
For issue 2, there are a few ways to approach. First, your application could directly download the PDF of the envelope (https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopedocuments/get/) and display that. If you would like to take the sender to a DocuSign interface to allow them to view the envelope, there are various Recipient View calls that may be of use: https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopeviews/
I would recommend testing the SenderView call to see if that meets your needs. An alternative would be the RecipientView call, which can be used with the sender's name and email in the call body to get to a read-only view of the envelope.
Does IBM Domino track the last login date for web users(UserName/Password and internet certificate)? I know the access logs contains this information but wanted to know if there may be something built into Domino (maybe in Address Book). Trying to come up with a method to disable web accounts that have not accessed a domino server in a specified time period.
Thanks,
Kev
The User Activity area in the Database Properties picks up from the log.nsf, which is where this information is stored. But, typically, the log.nsf will only have a few days' worth of information. When I've had this requirement before, I've manually captured it via a custom login page or an initUser function I've had in applications.
One of the easiest solutions is to trigger an action from a live web page that generates a database.nsf?openagent event.
like:
or
Ideally you've use the openagent to print a content type and a response, but if you don't browsers do pretty well with invalid responses from servers.
inside your "myagent" you will have the users name available to you to write it to a document.
Your next challenge will be in getting the agent to trigger, but, not too often, ideally only on login.
When a user uses a custom login form it submits the username/password and redirection url in POST method. You could change that to ...?openagent&nexturl=/blablabla.nsf
Your tiny little agent would run one and only one time upon login and update a document in a your custom logging database.
That's a developer's solution.
There are also admin solutions. The server does keep track of active web sessions, but, it does not drop them into the log.nsf like it does upon session ending for a notes session. I don't think it would be too much work from an admin standpoint to get that information there are a lot of event triggers available to you. It's just been way too long since I worked on any server that anyone cared about statistics.
Using the API, I generate the document and place my tags. User goes to sign and decides to finish later. It passes an event="cancelled" to my callback. I make note in my system that they cancelled it. But how can I get them back to the form later? There is no "authentication" with this. I do all the authentication on my end. So I need a URL to send them back to. Using the URL the api gives me to load in iframe expires. So how do I sent them Back to document?
I use PHP by the way.
Here are 2 possible causes (there may be others):
A 'Signing ceremony UX URL' has a short time to live (300 seconds or less I believe) so ensure you are making the call to retrieve a URL right when the user intends to perform the signing session.
A 'Signing ceremony UX URL' can only be rendered once. Verify that you are in fact retrieving a new URL each time and not reusing the original URL.
See this recipe from the DocuSign Developer Center. Repeat step 3 to retrieve a new URL to present to your user.
I'd like to trigger the in-webpage refresh button programmatically for the purpose of applying labels to emails without making the user manually refresh the page or make some other page action in order to see the labels. Is this possible to do? All of the documentation I am finding is surrounding refresh tokens, which is obviously something different.
Thank you for your time.
There's no way to do that from the Gmail REST API (i.e. trigger refresh action in web browser viewing the gmail page). If you're running as a browser extension on the other hand, then sure.