In my sharepoint site I have a document library with a workflow attached to it.Once any user upload a new document workflow is started and the document is send to approver for approval along with this an email has been sent to the approver for new document pending for approval. Now then email is sent from the mail server I have configured in sharepoint. it works fine. Now my question is I want to send the email to the approver from users email ID so that the approver should know from whome the request is come from.
Can any one help me how can I configure mail server so that the outgoing emailing should be done from users email ID.
Thnaks
sachin
You will need to set up a custom workflow with a custom activity to send the email rather than using the out of box approval workflow. This is one of those cases where a small change from the normal SharePoint way of doing things means a lot of extra work - the sort of problem I usually solve by telling the client it can't be done or is very expensive.
As an alternative, just including the requesting user name in the body of the email would be a lot easier and may be close enough to meeting the actual requirement.
You have write an event handler for the document library. You will have to send the approval mail using this event handler instead of thw workflow.
This post has some info abut event handlers in MOSS 2007
Related
I'm sending approvals via email in a Microsoft Flow. And I need to solve a task: how to send more than one approval all in one email (daily).
Does anyone know how to do that?
MS Flow (Power Automate) Approval connector which sends an actionable email to Approver is meant for single record processing and not for digest of requests.
We can store all the Approval requests in a list and send out an email by iterating through them every 24 hours (daily), or listing the Approval requests in email body and having “Approve All”, “Reject All”, “No Action” as responses to take action on them.
Based on the response, you can take action on items list. Read more
The best thing would be using mobile app to see the list of push notifications & approve them. Solve the problem by user training.
Approve requests on your mobile device by using Power Automate
I'm developing a ASP.NET application which integrates with GMail API and Google Calendar API. It uses a GSuite account to manage calendar events and e-mails.
Basically the application sends e-mails, invitations to people creating calendar events and, if an attendee declines the invitation, the application unsubscribes the user from the event and deletes the invitation.
The issue: everything works fine if the attendee uses GMail, else the declination is not received:
the attendee receives the invitation in GMail and selects "No" as response: the response is received
the attendee receives the invitation in another mail client and clicks the "No" link inside the mail: the response is received
the attendee receives the invitation in another mail client and rejects the invitation with any button provided by the mail client: the status in Google Calendar remains "awaiting response"
I found this behaviour using a standard GMail account too, so I suppose it does not depend on GSuite or my code. I googled a lot to see if this is a known issue, but I cannot find anything.
Does someone know if it is a known issue or there is any solution or any option to activate support for event responses?
Thank you very much for your help!
EDIT
I finally found the following:
the application creates a new calendar for managing its events -> invitations are managed as if they were from a different user and responses from attendees are sent to a xxxx_xxxxxxx#group.calendar.google.com e-mail address instead of the user's e-mail address, so no mail in GMail, no attendee status changed
using the primary calendar, I receive the event responses in GMail, but event attendee's status is not updated
with the second approach, I will try to take actions on new mail messages too.
As much as I can understand Google only supports responses to events using the "Yes", "No" and "Maybe" links in invitation e-mails, but what if a user uses a mail client like Outlook, etc.???
Please note that not all users are smart enough to understand that a link has to be clicked instead of buttons provided by mail clients and, anyway, I would expect that it works too.
Need help to understand the Kentico email notification flow on check-out process.
I used the PaymantForm webpart, on click of "Paynow" button, order confirmation email sent to customer before the payment step completes.
How to restrict this and how to send the order confirmation mail only after the payment is done.
Payment Gateway: Paypal
Kentico Version: 10
Please suggest.
Thanks,
Sharath
This email you're talking about is simply stating the order was created, no completed. You can look into the E-commerce module and check out the overall e-commerce settings. In there you can define your order statuses. With each order status, you can define if an email is sent or not. I'd suggest starting there.
How do I schedule a task to generate a weekly report in ServiceNow and send as an email.
I want the same report to be sent to my SharePoint site automatically every week. How to integrate it ? Please help.
You should be able to setup Incoming email on a Document Library in SharePoint and email a scheduled report to it from ServiceNow.
This also depends on ServiceNow being able to send email to this address.
You may need ServiceNow to have a VPN to your network with SharePoint, and you need Incoming email to be configured on your SharePoint install.
If those are working, you can do something like the following.
SharePoint
Create a Document Library
Go to Library Settings
Open Incoming E-Mail Settings
Change Allow this document library to receive e-mail? to Yes
Give this an E-mail address: reports#mysharepoint.com
SharePoint Security
Consider how ServiceNow is sending email to you. If email is sent via their mail servers, you may need to set incoming email option
E-mail security policy to Accept e-mail messages from any sender
In this case, be mindful of what email can be delivered to your network. This may allow unwanted emails coming in.
If ServiceNow uses your mail servers, you may be able to grant access to the Document Library for the user that is delivering your email. If so you may be able to set this
E-mail security policy to Accept e-mail messages based on document library permissions
This is much more secure, but these things always depend on your environment and your needs.
ServiceNow
Go to Reports > View / Run
Open the report to be delivered
Click the dropdown on the Save button
Choose Schedule
Fill out the Schedule form
Click the Users lock
In Enter email address put in the email to send to the Document Library (ex: reports#mysharepoint.com)
Run: Weekly
Choose the Day of the week and the Time
Subject: My report
Right click the header and choose Save
Test this by clicking Execute Now within the Scheduled Report
I am using the embedded sending interface to send DocuSign envelopes.
There might be the case where different senders assess the same envelope through the embedded sending interface. (for example the first user does not send and the second user comes into the application page)
I have tried enabling the Sharing permission but the users are redirected to the Manage Envelopes Inbox page instead of the embedded sending interface.
Any suggestions on how I should go about to do this?
Perhaps the answer is to back up a step:
Your app can show the documents to the user for approval. If he approves, then he sends the envelope. If he thinks someone else should review/send, then he re-assigns the task to his colleague for her to review/send.
The issue is that once a person starts the sending process, it is tricky to undo it.
I suppose the first person could simply not send and then your app could void the envelope and create a new one for the other person to review/send. But I think that would give a poor UI.
Also, are you sure that you need the senders to use the embedded signing view? It is often a much nicer UX (user experience) if your app can entirely send the envelope on behalf of the signers.
Your app has the most "domain knowledge" of what needs to be sent. Any per-envelope changes can be mediated between the senders and your app. Then your app creates the right envelope and documents.