Th11: This session explained what state machines are, whyto use them, how to create them in Visual Studio and other products, and how to redesign a number of workflow models as state machines instead.
Recently, we’ve been working with a customer on a particularly interesting use case for SharePoint that I thought others in the community might be interested in learning more about. The customer is using Zantaz (from Autonomy/HP) for email archiving with a primary focus around eDiscovery, email retention and legal hold. A number of factors are driving the review their current implementation, including its age and cost to maintain, and concerns about the recent flux in HP strategy
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.
It is strange how many developers wince when they face SharePoint and become melancholy when talking about workflows. Workflows are not just like programming, or something very special or something very complicated or something very limited or something for documents. Some people tried to solve simple tasks with SharePoint workflows, but failed somewhere when it became clear that they cannot read the manual from the middle and they have no time to read it from the very beginning.
This is an article that was submitted by Gene Vangampelaere for the European SharePoint Conference – Top SharePoint Competition. Gene is a SharePoint architect/ developer in ana educational institute. He works mainly on no-code-solutions.
I always encourage the power users to build their own applications by using the out-of-the-box tools. The more advanced applications need the assistant of SharePoint Designer to create workflows. In some cases the OOTB workflow actions are to limited.
When we consider the development of an application on the SharePoint platform, such as issue tracking, automatically think of the workflow that will control and manage the lifecycle of information, in this case, the issues that can occur.
But if we go down a little into the functional requirements we can see that other elements are almost as important as the workflow, and this elements need specific solutions and tools for their resolution.