Is it time to extend your SharePoint Workflows?

One thing a lot of clients ask me:  “When should I start looking at a 3rd party product for my SharePoint Workflows?” This can be a tricky question sometimes, as the answer always comes back to: “It depends on what you want to do and what your requirements are.” But I figured I would at least try to compare SharePoint Native Workflows with what would be logically the product that would extend workflow functionality in SharePoint, but not replace it:  Nintex Workflow. []

The Future of SharePoint – What we learned

Microsoft today announced the General Availability of SharePoint 2016, with a live streaming Event from San Francisco.  But what they really announced was their vision for the future of the platform, and some of the new features we can expect to see from SharePoint this year.  What are some things we learned from this announcement? Mobility is (still) a huge focus Responsive Design SharePoint from a UI/UX perspective is changing once again, but finally to provide a much richer mobile experience.  New Team Sites, []

When to avoid SharePoint Online

Sure, I’ve extolled the virtues of SharePoint Online, and how it can make a lot of sense for organizations as opposed to On-Premise SharePoint installations.  But, there are still other reasons why you should consider an On-Premise environment for Share Point.  Let’s examine a few different reasons: Performance Limitations While SharePoint does set some hard limits for certain things whether you are On-Premise or in the cloud, some of those limitations can actually be changed if you have deployed an on-premise environment. []

Build a SharePoint Workflow to Notify on a Periodic Basis

So, here’s the user story:  You have a list that contains some time sensitive material.  In this case you want to make sure your users complete a particular task on time, and if they don’t, make sure they get notified after 1, 3, and 5 days after the due date has passed. How can we leverage SharePoint workflows to accomplish this?  Let’s build it! You must use SharePoint 2013 Workflows We’re going to be calling a loop during this workflow, so it’s []