The article is a continuation of the post describing creation of a simple newsletter using SharePoint Designer 2013, written here and the other one using Nintex Workflow for Office 365, written here. This time I would like to show, how the similar solution can be made using Microsoft Flow and SharePoint Online.
I was working on my newsletter’s solution, aimed to automatically send prepared messages hosted in my SharePoint. Naturally, newsletters often contain images. Lots of them frankly speaking. The most straightforward approach was to insert them as a URL to the physical file stored in SharePoint (described here). However, in that approach, if a recipient has no access to the site, where the file is hosted or is not yet logged in, the images won’t show up.
I have recently found myself in a situation, when after creation of a new, Modern Site (it was a modern Team Site) my account, even though that was set to be a SharePoint Administrator (even a tenant one :)) and a Site Collection Administrator wasn’t able to see links to any galleries in the Site Collection settings. Moreover, when accessing them using a direct links and then trying to ex. add a new solution, I was being told, that I have no permissions for that operation.
The article is a continuation of the post describing creation of a simple newsletter using SharePoint Designer 2013, written here. This time I would like to show, how the similar solution can be made using Nintex Workflow for Office 365.
Some longer time ago I was asked to think about a solution, allowing my client to notify his employes, about changes and news that were being published in the application built on SharePoint 2013. However, client did not want to use alerts, or to develop a dedicated application. No – the client wanted something like a newsletter, which would allow him to sent HTML formatted messages to all users (or SP Groups of users) who were working with the application, or to anyone having account in SharePoint (or to anyone beyond the organization).
In Nintex Workflow for SharePoint (every version), when you use the “Flexi task” action, that creates and assigns tasks to specific users, if you (as a viewer) are not the assignee, workflow tells you that “You are not authorized to respond to this task.” – then to make yourself authorized you have to click the “delegate” link, then to reassign that task to yourself.
Workflow constants are a feature available only in Nintex Workflow for SharePoint on premises, allowing you to store globally used workflow variables in a single place. These variables can be then used across all web applications and site collections in your SharePoint Farm, or just in a single site – depending on the scope where they were created.
There are numerous use cases where Workflow Constants can be used: keep user credentials used for authentication in actions, keep thresholds for approvals, or keep specific dates, which are important for your company operational processes and many more, generally related to the “dictionary” purposes.
The Microsoft Ignite 2017 conference has just ended last week. It was full of very interesting keynotes, presentations, workshops and demos. I haven’t had the opportunity to be there myself, however I was trying to follow up Twitter and all content being published during the event. This is my summary of the most interesting announcements, specifically for the SharePoint and Office 365.
I’m proud to announce that I have been honored as a Nintex vTE! I’ve became 1 of 70 workflow professionals from the global network of Nintex partners!
Have you ever faced that issue? When your workflow is running smoothly and out of nowhere it gets suspended? Then when you hover the “i” icon to get more details you are informed, that “The workflow instance was too large to persist”? Well I had. Here is what I found and how I recommend to solve it.