Use Sharepoint Designer:
In the body of the form "send an e-mail", find 'edit hyperlink' button in the upper right corner of the message.
for field address, click lookup for string or 'fx'
in Data Source, select “Workflow Context”.
for field from source, select "Current Item URL".
Now Save, publish and test.
Workflow it is. A very simple one should suffice.
In the explanation below I'm using SharePoint 2013 and Office 365, but it's absolutely the same in SP2010 or/and on premises, and even in SP2007 the process is very similar.
You will need SharePoint Designer installed on your computer.
Open SharePoint designer
Open your site
Go to ...
Yes, you'd just need to craft a hyperlink to the edit form in the email body.
<a href="http://your.domain.com/sites/sitecollection/Lists/Tasks/EditForm.aspx?ID=[Add current item id here]">Edit item</a>.
Use the SPD interface to add in a workflow variable for the current item ID or task ID in the URL above where the  are.
There are several alternative approaches available to send Emails.
General Email Sending method
SharePoint Client Object Model (CSOM)
Using general Email Sending method
This is the usual method to send email in asp.net. There are advantages over the other two methods.
Send attachments to the recipients
Send emails to ...
When you add a user / group in SharePoint, you should see "Send an email invitation" check box to control whether or not send the welcome e-mail to the new users.
You could clear that check box and it should fix your problem.
Also, there are some situations when "Send an email invitation" is hidden.
I checked dialog's code-behind by reflector and find that:
Here is my implementation of Vedran's answer:
First, in a feature receiver, I swapped the Event content type with the Schedule content type to take advantage of the Attendees field (and the cool Free/Busy field!):
SPList list = lists["Calendar"];
SPContentType newContentType =
By default, there is no logging mechanism in SharePoint for outgoing mails.
Mails in SharePoint are sent by giving an SMTP sever IP address in Central Administration. SharePoint never sends email directly. It relays or routes mails to the SMTP server. So, logging should be done in the SMTP server itself.
There is also another way of doing it. You can ...
I think I found a solution for appWebUrl. ssdar's answer gave me the same problem as I initially had with loading different pages, but another answer in the thread they linked to contained an answer that led me to the right path.
var appWebUrl = decodeURIComponent(getQueryStringParameter('SPAppWebUrl'));
var hostUrl = decodeURIComponent(...
There is a lot of very useful information from Microsoft but SharePoint Alerts are counter-intuitive on a lot of levels. The number one rule when dealing with them is to never assume that they follow a predictable pattern because they do not and will surprise you every time. They also love to work perfectly for 100 days straight, then for no discernible ...
The System.Net.Mail namespace works with on-premise Sandbox solutions but does not work with Office 365, so there is no way to send email from code. The "Send Email" activitiy in SharePoint Designer workflows in Office 365 does work, so yes, you can use workflow to send email.
Might I suggest switching to using the System.Net.Mail.MailMessage object instead of SPUtility. SPUtility.SendEmail is a good shortcut but, as you've seen, you lose a lot of control over how the message is sent and formatted. The MailMessage object gives you that back but does require just a tiny bit more work.
To answer your specific question, the ...
If you want to get all the users in your SharePoint site you can use :
Try using below endpoint to get the Site Members from Members group:
To get the specific property for user, you can add $select query as given below:
You have to change a system setting that allows workflows to run when emails are received in an email-enabled doc lib. Other than this, System Account is not allowed to run workflows for security purposes. It will only work when an email is received, not when an item is edited by System Account. You should not be editing items with the System Account:
Couple of things to check:
Make sure "Microsoft SharePoint Foundation Incoming E-Mail" timer job is running on the server where SMTP confgiured.
From Central admin, Incoming email setting > advance setting, make sure drop folder path added here.
Make sure Timer Services having the correct permission on drop folder.
If you want to customize the sender email address, then you cannot use SPUtility.SendEmail -- you'll have to use the System.Net.Mail framework classes.
Under the covers, SPUtility calls a method named "RemoveFriendlyNameFromEmailAddress" :(
As a developer you have several ways to customize the alerts.
In order to insert your company's logo, you will have to implement your own iAlertNotifyHandler.
You can get an overview about your possibilities here: "msdn Library > Alerts in SharePoint Foundation"
The article says nothing about SharePoint 2013, but when you look in the documentation for "...
Office 365 does not support incoming e-mail to lists and libraries. Sorry.
There are third party addons which can allow this, but they all cost money.
Can u try to add a pause for 14 days before the loop 1 and add a pause for 14 days in the if condition block, under the email statement. The last pause which is already given in the workflow should be removed. Let me know if it works. And make sure to tick in the workflow start option Item Created.
let me know if it works o not. Thanks.
I have not had an opportunity to try this, but there is a constructor of SPUtility.SendEmail which accepts a StringDictionary of MessageHeaders.
According to this link, these are the 3 headers Microsoft uses to create a high priority email.
X-Priority: 1 (Highest)
So to use it with SPUtility.SendEmail, use this ...
I had same problem, after all I changed in Configure Incoming E-Mail Settings->Settings mode to -> ADVANCED and specified E-mail drop folder Path :c:\inetpub\mailroot\drop. I hope this answer will help somebody :) .
On a multi-server farm, be sure the "Microsoft SharePoint Foundation Incoming E-Mail" service is running on the same server you're using for the SMTP service, presumably one of your front end servers. Check this in Central Admin-System Settings-Manage Services on Server and cycle through your servers on the top-right. In my case the above mentioned service ...
The following solution worked for me:
In the body of the WorkFlow email, position yourself where you want the link to go
Then click on the Edit Hyperlink button in the top right of the window
In the address, paste in the URL to your EditForm for example:
Then select the string builder button (....
You can try creating a dynamic string and place that column in the configuration of it and then using that variable in your CC section.
Add a step prior to all the email steps
On this step, use the action "Build Dynamic String"
Click the 'dynamic string' link in the new action, to open the "String builder" dialog
Click the "Add lookup..." button
There is no possibility to send Attachments using this method. But you can use of SPAdministrationWebApplication to get the SMTP server details.
Here is the sample code:
//Get the Sharepoint SMTP information from the SPAdministrationWebApplication
string smtpServer = SPAdministrationWebApplication.Local.OutboundMailServiceInstance
With SharePoint Online you cannot enable incoming e-mails on a list, but you can create a site mailbox:
I got round this issue by using Infopath Designer to inject the filename into a "single line of text" field that my workflow could target.
The steps were as follows.
create a "single line of text" field in your list. I called mine "AttachmentURL"
Load infopath designer. and load your SharePoint list
Right click on the "single line of text" field "...
I wouldn't do this with workflow, I would do this in a PowerShell script that runs on the server, set it up in a Task Scheduler, and let it run every Monday. The script would kick off the workflow that you want, or alternatively use the PowerShell script to compile and send the email instead of the workflow.
Add ?subject= at the end of the mailto link and then add the subject line, replacing spaces with %20. So if you want an email link to go to email@example.com with a subject line that says "this is important", you would format the link as follows:
you can also add body text by appending &body= and ...