Good afternoon,
I am integrating DocuSign into our business applications (node.js) and have an issue:
Is there a way to use the DocuSign connect webhook to let me know when a workflow is paused? On the admin connect page, I have all possible boxes checked on the connect options - which do not include anything about workflow status (mostly signed/delivered/completed/declined stuff).
My current workaround is to add a customField on the Signer 'pauseAfterSigned' which I check for in the webhook xml. If the signer with that field has Status "Completed" then I know the workflow has been paused. This seems like a lousy workaround :(
We currently don't have an event fired when a workflow is paused as far as I know. So your workaround would have to do for now. Can you please provide more information around your scenario? Perhaps it's something we should consider adding depending on the scenario here. Thank you.
Related
Is there a way we can trigger AWS Lambda function from Microsoft Teams. what I wanted to achieve is that stakeholders be able to approve merge requests from MS teams or maybe give an approval on Production rollout.
Is this connection possible at all?
Please help
Yes, this is definitely possible, but there are a bunch of things you need to do to get a full working solution, so it's hard to give it all in one answer here. Here are some guidelines to get started though:
You need a something for the user to actually "Approve", and way to do this. A common approach is to send a "Card" to Teams, which can have an "Approve" button. There are a few different kinds of cards, and different ways to send them to Teams, including a Bot, Flow/PowerAutomate (which uses it's own Bot behind the scenes) and incoming Webhooks.
When the user clicks the "Approve" (or "Reject") buttons, you need a way to handle the action (to link the button click to AWS).
If you've built Bots before, this might be the easiest option. If you want to use Flow/Power Automate, that's another option (see here for more information about important changes due "this quarter" - I'm not sure if they're released yet). If you've not used any of these, your best bet might be:
Configure an Incoming Webhook
Send a Connector Card with a "Post" button
Set the POST url to be your AWS Lambda
I can't seem to find any way in the Quire API doc to mark a task as unread (i.e. appearing with a red/orange dot next to it in the Quire app). If it does not exist, it would be a useful feature to implement in order to allow the user to detect a change made through the Quire API.
Best regards,
Rafaël
The "unread" indicator behaves in the same way when using the quire-api/browser or mobile clients. It shows when a new task or comment was added by another user, through either UI or api.
Neither the UI nor the quire API have a function to explicitly control this status indicator.
So as of now it would not just be a "new/missing" api feature first, it's rather a new completely new Quire-Feature, which had to be implemented first. You can post your feedback and ideas in the Quire Feedback project (keyword 'orange dot') or send an email to info#quire.io / support#quire.io.
So as of now you can trigger this by adding a comment or add a new task via API.
A workaround I found is to add a new task and to set asUseras true as explained in https://quire.io/dev/api/#operation--task-id--projectId--post. Then, the task will be marked as unread
Can anyone help.
I’m using the rest api to create an envelope, and then configure it using the api sender view call (/restapi/v2/accounts//envelopes//views/sender) to get the DocuSign UI.
Creating the envelope and viewing it the first time using sender view to bring up the docusign api works fine.
The problem occurs if instead of sending the envelope I click ‘save as draft’. When I try to go back to the envelope and view it again using sender view I get the following error with http status of 400:
{
"errorCode": "EDIT_LOCK_ENVELOPE_LOCKED",
"message": "The envelope is locked. The lock must be released before requesting the sender token for envelope, id = xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx."
}
The lock seems to wear off after time (apprx 20 mins). However after it wears off I can only view the item once, and then the lock is reapplied.
I can’t find anything in DocuSign api documentation that relates to this behaviour. Any help would be appreciated.
UPDATE (12/Feb/15): This error only happens on my demo account but not on production, so it seems like it's an account setting, but I can't figure out what/where the setting is.
Thanks,
Nick
Yes - there is new documentation about this envelope locking feature and behavior in the February service pack (PDF) available here: https://www.docusign.com/support/releases.
We have a bug logged on our side where Save Draft isn't correctly releasing the lock on the envelope. We should have a fix for this issue in our DEMO environment soon. The locking feature is currently only "ON" in our DEMO environment but not in our Production environments while we find and fix potential issues such as the one identified here. More information about locking is in our February service pack (PDF) release notes available here: https://www.docusign.com/support/releases.
We use Salesforce and Google Apps.
We have a Google Apps Email account that accepts an email and forwards this on to Salesforce, where Salesforce creates a case.
The last 2 fridays, we have had problems where it can take over 3 overs for an email to make its way into Salesforce.
How do I find out if the problem is with Google Mail not forwarding the email on in a timely manner, or the problem is Salesforce not processing it in a timely manner?
Anyone else ever had this problem?
Thanks!
A few ideas, which you may have already tried:
1) You could check the timestamps in Gmail to see when the emails were received and then forwarded to Salesforce to see if there was a delay.
2) You could check the dates against the Salesforce system status page to see if there were any reported issues: http://trust.salesforce.com/trust/status/
3) Same for the Google Apps status page: http://www.google.com/appsstatus
4) Check to see if there were any other delays in Salesforce or concurrent batch jobs that might have caused the delay.
5) Submit a support request to Salesforce to inquire.
Hmmm. Are you using Salesforce Email to Case? Here's someone posting a similar question: https://success.salesforce.com/questionDetail?qId=a1X30000000IGwWEAW. It seems that at the time that both problems were a temporary outage on the part of Salesforce. Also, are you using any apps to integrate Gmail and Salesforce? Because apps like The Scoop Composer allow you to forward emails and create cases right away. http://www.cloudgizmos.com/salesforce-gmail-integration. Hope this helps!
I am creating a C# event handler for SharePoint 2010 (sandboxed solution). When the ItemAdded event is hit, I have some logic that I perform, and then I would like to send an email.
Unfortunately, it appears that SPUtility.SendEmail and System.Net.Mail are not allowed in sandboxed solutions. Is there any way around this? Thanks.
You are correct according to the documentation SPUtility.SendEmail is not available in a sandbox solution.
The solution would be to create a full trust proxy that can send the email for you.