Home » OneDrive for Business » More on Quick Steps for OneDrive for Business, Office 365

More on Quick Steps for OneDrive for Business, Office 365

An entry to the help section of Microsoft’s Office web site titled “Automate common or repetitive tasks with Quick Steps” presents this new feature of OneDrive for Business, as originally introduced with Outlook 2010.

As the article makes clear, Quick Steps were intended to reduce the repetitive nature of performing tasks, for users, with automation very similar to workflows. But what is very different between the two versions is the lack “packaged” repetitive actions in the OneDrive for Business version of this feature. As this writer wrote in an earlier post to this blog, Quick Steps for OneDrive for Business are actually built on workflows, which, in turn, need to be put together with a tool like SharePoint Designer, or Visio.

Quick Steps are available, as a group, in Outlook 2013. In contrast, the user, presumably, is expected to create a set of Quick Steps for OneDrive for Business. Once these automated processes are exposed on the Ribbon, they can then, perhaps, be quickly modified, as required to meet new needs.

Certainly one would hope Microsoft will soon offer more information about Quick Steps for OneDrive for Business. A search of Office.com did not reveal any training material for OneDrive for Business. But this writer did note a number of video presentations on how to build Quick Steps for Outlook 2010, or Outlook 2013.

There is an article on the topic available on MSDN. This article is authored by JongHwa Lim “from the SharePoint Design team”. The article title is How to Create a Quick Step and Custom Action to start SharePoint 2013 workflow. Based on Lim’s opening sentence: “Today, I will share with you a feature for creating a Ribbon button on a SharePoint server UI. This button will start a SharePoint 2013 workflow when pressed.”, it should be clear to readers the article will offer useful information on this topic.

Our quick read of Lim’s article did not produce any hard coded steps, so SharePoint stakeholders strictly looking for a no-code approach to implementing this feature may find what they are after in Lim’s article.

Ira Michael Blonder

©Rehmani Consulting, Inc. & Ira Michael Blonder 2014 All Rights Reserved