Are you looking to reach key decision makers in the SharePoint, Office 365 and Azure space? Then the European SharePoint, Office 365 and Azure Conference is the place for you. Here you can find one of the largest SharePoint, Office 365 and Azure Expo Halls in Europe, showcasing innovative solutions and exciting product/service updates. Connect… READ MORE
Steve Fox, Director of Developer and Platform Evangelism at Microsoft, shares his thoughts on the one thing that people need to know about SharePoint 2010. This is part of ‘The One Thing’ video series produced by Christian Buckley (@buckleyplanet) and the Axceler team.
Recently I wanted to figure out how to show or hide a custom developed SharePoint Ribbon Tab based on the permissions of a logged in SharePoint user.
I have a custom SharePoint 2010 Ribbon Tab with the title ‘Show or Hide Tab’ and I want to hide the tab if a current logged in user is a member of the ‘Root Visitors’ security group.
I do not want to hide the entire ribbon and I also do not want to hide only the inactive buttons. The standard ribbon tabs like ‘Documents’ and ‘Library’ must be visible for all users and audience targeting must be applied only against my new custom ribbon tab.
I can imagine that the requirement is quite a common one. You might want to develop a set of custom tabs which are only visible to users who are members of a specific SharePoint group.
SharePoint is a great tool and adding workflows to it makes it a marvelous one. Tasks automation and process streamlining mean less work and much efficient information flow. Unfortunately, like with any powerful tools, deploying workflows in a wrong manner can lead to results opposite than expected. There are many ways to achieve given functionality, but only one can be the optimal one. With so many switches and levers available for workflow designers, working on top of highly customizable platform like SharePoint, process implementation can become a disaster if performed without basic knowledge about workflow architecture and environment it works in. And usually it does not matter if you use SharePoint Designer, Visual Studio or third-party tool to define the workflow.
If you are responsible for designing and implementing workflows read on to learn about five most common things you can do to turn your workflow solution into a failure and, fortunately, advices how to avoid these traps.
