send-email | Easily send email using any major email service provider | Email library

First off, the most efficient way to send the same email to lots of users is to send it to yourself and BCC all the recipients. This will let you send one email to the SMTP server and then it will distribute that email to all the recipients with no recipient being able to see the email address of any individual recipient.

Second, you cannot use timers to reliably control how many requests are running at once because timers are not connected to how long a given requests takes to complete so timers are just a guess at an average time for a request and they may work in some conditions and not work when things are responding slower. Instead, you have to actually use the completion of one request to know its OK to send the next.

If you still want to send separate emails and send your emails serially, one after the other to avoid having too many in process at a time, you can do something like this:

@Sam H's comment is correct: use context as a positional param instead of passing it as a keyword param with context=context.

I'll explain it with an example. Let's say you have a function to add up two numbers:

You need to have a shared storage that all members of the process can access, the file should then be opened and updated from there

My recommendation is (if your company teams/365 groups are set up well) to just use a specific folder in your team's SharePoint site (O365 group) that will be accessible via teams, a browser, or any of the applications required.

This can then be done in the approval flow you're playing with, or via one or several approval flows within the context of a BPF.

Those methods:

1. Approval Flow
2. Business Process Flow (BPF)

This won't be hard to sort out, if the people involved are only a few in a larger team, and the data is sensitive, then create a separate folder and restrict access. Otherwise, you should at least restrict write access, to ensure that only the people involved can modify the file.

As mentioned earlier, the only thing that could hold you back is the company's set up with regard to O365 Groups, Azure (and normal) AD groups, and the literal teams. But it really shouldn't be an issue for this.

If there is bad group infrastructure, then it's all good, you can just lean in to that and make another brand new team in Teams. Once you've done that, find the new O365 Group it creates, and then just manage it all from SharePoint (you can even add a tab in the Team client to manage the process!) to ensure that the permissions are just right.

Build the logic first. It should be relatively simple:

1. Person A performs their task, they click to say it's done.
2. Person B. Etc.

Then you can start worrying about the file, and how it's accessed and from where.

This is by far the easiest way to do things, and allows you to keep things as simple as possible. For the logic just plot it out step by step, then once you have that, take a look at it and see where you can economise it, and either loop elements, or use variables to make it not require the specifics that you begin with.

With any luck, you'll soon have it doing most of the work for you. You can even ensure that copies of the file are made at each stage and are then archived, if you like.

This is my preferred option because it will codify the process and you can make things however complicated in the flow(s) themselves, separately.

The BPF will ably show the organisation how your team performs the task, ie. Johnny edits, then Billy edits, then Jenna edits. However at each stage (or for bespoke tasks) you can call on different flows to perform whatever tasks you need performed.

There are positives and negatives to this approach, mainly:

• Positive - You can set it up without ANY automation, and you can use it to manage your current manual process.
• Positive - Later you can start to instill the automations you need to process what is required.
• Negative - This is advanced stuff, and it's not only difficult to learn, but it's difficult to get right. That said, the end result will be amazing.

If you just want to send "hi" for the subject instead of the value the user typed in the you just can hardcode it directly in the ajax method where you define the data:

Since jQuery 3.0, success: function does no more work as it has been suppressed, see https://api.jquery.com/jquery.ajax/ .

Deprecation Notice: The jqXHR.success(), jqXHR.error(), and jqXHR.complete() callbacks are removed as of jQuery 3.0. You can use jqXHR.done(), jqXHR.fail(), and jqXHR.always() instead.

But you can use this arrangement for the new sendMail():

Since emailRange.getValues() returns a 2D array you need to reference the actual string value by its indices, which in this case, [0][0] as the array has only one value.

To, From, CC and even BCC are just headers in the email. You can put in whatever you want, at least if you use a library that gives you control over the headers in your email.

Let's do a very simple example using telnet to send an email.

First, look up which email servers handle mail for a domain (here gmail.com), e.g., with host:

The documentation on Swift Mailer warns you about special characters:

If the username, password or host contain any character considered special in a URI (such as +, @, $, #, /, :, *, !), you must encode them. See RFC 3986 for the full list of reserved characters or use the urlencode function to encode them.

Execute a command looking like this to get the encoded password