I want to customize the docusign emails that are sent to the participants.
I'm sending the below:
SupportedLanguage = "fr"
as part of the Signer in the api call to create envelope. The "Enable custom email and language for each recipient" is checked, however the email is still showing up in English. I've learned that the user needs to set their locale settings to that language in order to receive the email in a different language. Can you help me with the specifics of how this needs to be set? Is it in the docusign account for the consumer or the user's machine? What else am I missing here?
The above line of code can be used to have the email for a specific recipient sent in French.
However, that only works if the person in question did not already decide to use DocuSign with some other language.
In other words - they can override your choice if they have their own DocuSign account and not also have it set to French.
Is it in the docusign account for the consumer or the user's machine?
It only depends on if the user in question is a member of any DocuSign account, i.e. they have credentials to DocuSign.
This blog post can be useful.
Related
In the last days, I have started to integrate DocuSign for SalesForce, and I have some questions and issues :
Can one define ahead and anchor the location for signature and other fields that the customer has to fill? So that our sales reps won't have to go through each document and plant the fields in the envelope, and instead it would be immediately ready to send?
Is it possible to define default Email sender as a Queue email/Department Email, and not the user email? Also, can the final email with the signed document be sent to the queue email?
Can I define the subject and the body of the email on Hebrew (it's a right to left language!)
Can I use in the email subject and body dynamic parameters from SF objects? Like from the opportunity or the account.
I did some tests, but the signed document doesn't show in the Document status section in the opportunity. What might be the reason for it?
Yes you can, you can set up a template with predefined tabs or anchor text depending on how you are using DocuSign here is the how-to: https://support.docusign.com/en/guides/ndse-user-guide-working-with-templates
That email address would need an account, personally I would not set it up that way, if the end goal is to get a copy of the final doc to that mail queue I would add that email address as a recipient (gets a copy)
you can set up custom languages for each recipient: start a new envelope, add recipients, in the Message to All Recipients, select Custom email and language for each recipient.here is the how to:https://support.docusign.com/en/guides/ndse-user-guide-recipient-language
Yes, custom buttons in Salesforce allow you to dynamically define the Subject and Email Message of an envelope using any field in the Salesforce object.
It sounds like your Connect for Salesforce may not be authenticated, look and see if it is for just one envelope or for all, perhaps disconnect and reconnect. DocuSign had a support article on this: https://support.docusign.com/articles/Why-aren-t-my-completed-envelopes-being-shown-in-Salesforce
I am implementing an email verification service, with the purpose of confirming that the person registering is indeed the owner of that email address (specifically, that they work at the organisation that the email domain belongs to).
I will send an email post-registration with a single-use link in it that will set their status to verified = 1.
Users can choose to register and log-in using either a simple email/password combination, or by using the Google Sign In service.
My question is: do I need to verify the ones that have registered with Google Sign In? In order to provide their email address to me, they had to sign in with Google, who then confirmed the address. Is there anything I've missed here, or can I immediately consider these users to be the verified owners of these addresses?
If you are using google sign in there is no need to verify the user.
Whereas if have your own login system, then you must verify the email because
if the email is not verified then you cannot have forgotten password feature through email
and also the user might not have actually had the email so anyone else could create the same email and if you have forgotten password through email someone else could easily access others data.
I have a .NET console application that add a list of users in a selected Yammer group through [/group_memberships.json] endpoint and it works fine.
Anyway the customer wants to avoid the sending of a confirmation email to user that has been added. In fact, after my program runs, all users receive an email like "XXX has added you to the YYY group on Yammer. Go to group".
The only way that I found to avoid this email is disable email notification in user settings.
Is there another simple way? Through Rest API is possible tell to Yammer to do not send email or, otherwise, change the user settings? I'm asking it because there're some hidden Rest API not documented in the official Yammer site.
Thanks
Yammer doesn't have any API endpoint to achieve your objective. Your customer may consider adding a rule in exchange to block emails based on the "from" address and certain keywords in the "subject".
I am new to Gmail api.My requirement is to change signature of the gmail account through my application.
Ex:
Now my account signature is
Ramprasad
And i want in this format
Ramprasad
I am not available from 26-12-2014 to 30-12-2014
How to get this signature through my application using gmail api
Thank in advance
Unfortunately the Gmail API currently doesn't provide a way to change your signature. There is an Email Settings API that does allow for this, but only for users within a Google Apps domain and only by the domain administrator.
I'm using Register with Facebook as one of the ways to log in to my web app, and expressly ask for the "email" permission..
On login, some of the user data ($facebook->api('/me')) is stored into the users database, however, sometimes the email field just doesn't exist - is this a common problem?
Just a guess...
The facebook documentation says:
note: this field will not be returned if no valid email address is available for the user
Source: https://developers.facebook.com/docs/reference/api/user/
So when an email address become invalid (users who haven't used facebook in years and have destroyed/changed their email address since for example), facebook may stop returning this field.
5% of invalid address may sounds big, but if I check my facebook friends, I think more than 5% of them never use their account, and I wouldn't be surprised if the address they used when they signed in is now invalid.
Users don't always have to provide an email address in order to use Facebook. They can also sign up via SMS, though it's far less common.
In short, FB won't always have an email address, so can't serve it to your app.
Try:
// Just to make sure email are permitted
//$facebook->getLoginUrl(array('req_perms' => 'email'))
// Request email
FB.api('/me?scope=email', function(response) { /*...*/ });
Or:
$email = $facebook->api('user_id?fields=email');
PROBLEMS:
The user changed the visibility of its email address to "only me" and thus you have no way to get it.
The user registered with SMS instead of email as mentioned in the previous answer.
ALTERNATIVE:
If you absolutely need to contact the user but you cannot get its email address nyou can still get its Facebook email (everybody has this email): "user_name#facebook.com".
If the user uses a POP server he will directly receive the email in GMail or others, if not he will receive your email as a private message. The only drawback if this method is that your email must be "plain/text" and not "HTML".
One thing is Users don't always have to provide an email address in order to use Facebook(could have registered through mobile)- as mentioned by Colm. Apart from this-
Please check that if the user has definitely granted you the email extended permission or it hasn't subsequently been revoked. To have a check on this you could use the permissions api-
/USER/permissions
I had similar problem & I found the cause for this. This problem occurs for users who have not set their Primary Email Address (They have many email address but they haven’t pointed out which is their primary email address) under General Account setting tab.
I tried using such accounts on various famous sites which has Facebook login & even they couldn’t retrieve the email address from such accounts.
So, its not the problem with the code(Assuming u have asked for permissions). We just have to handle such scenarios & let users know that we didn’t receive their email address. Like Klout does.
Thanks
In addition to what #Jigar Jain wrote above, users can actually uncheck the email permission during the sign inflow. If that's the case, his/her email address will not be returned by Facebook.
It's up to you to implement a logic that makes login unsuccessful if user unchecks the email permission, to force your users to choose another login method that will guarantee that a return of user's email address.
It is not mandatory for someone to give their email address while signing up with Facebook. An alternate approach would be to ask the user to link their email id in the Facebook account settings. That way you can fetch the email id, if that's a mandatory field in your DB. Otherwise you can continue with the id provided by FB which is unique.