The essence of a WorkFlow is the progression of steps (tasks, events, interactions) that comprise a work process, which involve two or more persons and creates or add value to the organisation’s activities. In a sequential workflow, each step is dependent on occurrence of the previous step; in a parallel workflow, two or more steps can occur concurrently.
As you can imagine, these can can get quite complicated rather quickly. Naturally, you are going to need help in depicting a sequence of operations, the work of a person or group, the work of an organisation of staff, or one or more simple or complex mechanisms.
Therefore, this category is full of handy tips, tricks, advise. Check out some of the Step by Step blogs or learn from our eBooks, how to videos and webinars.
Since my early days working in MS-DOS, I have enjoyed the tricks of shell-programming or shell-scripting. Being able to tell a machine to do a set of sequential actions in one go, often repetitive tasks, can be a life saver, and sometimes, a way to do something that other APIs won’t allow.
This post will focus on PowerShell, specially oriented for the SharePoint ecosyste
Organizations aiming to implement workflows in SharePoint usually require to properly handle the forms part, whether with InfoPath, third party tool or one embedded into workflow solution (2 in 1). That’s the precise moment to figure out a strategy regarding forms. Once technology is chosen, it might be too late.
There are many ways of using jQuery in SharePoint and calling web services. We will try to look at how smartly we can do this. We will use the Visual Studio to complete all of these steps.
Since Microsoft has moved to a Cloud first approach with Office 365 some challenge came to light when it comes to the handling of events in SharePoint 2013 (Online). In the good ol’ days we would open up our Visual Studio and without hesitation write an awesome Event Receiver and deploy it as a Farm Solution. These days are over as we all well know.
In exclusive interview IT decision makers share their story and lessons-learned during workflow development.
The independent K2 whitepaper entitled ‘Build and Run Reliable SharePoint Workflow Apps’ looks at despite the addition of new features, workflow in SharePoint 2013 remains limited in many scenarios.
Our lives are dictated by the latest technologies, such as workflow software, with providers offering us solutions and applications that we never knew we needed. As a result, our corporate models mimic the convenience and pace at which we live our day-to-day lives to match how we conduct business. In a world that’s become increasingly mobile, the changing workforce requires faster, more agile workflow software.
Having a good workflow running smoothly isn’t good enough. A successful workflow requires good user experience in which end-users can easily find what they want and quickly adopt from the beginning.
There are many reasons why a workflow deployment fails. It may be the cause of a bad process or end-user engagement during the project. Having no good communication commonly causes the failure as well. However, apparently people rarely realize that if the flow is complicatedly designed, it will damage the whole workflow deployment. For example, operation department in a company gave its IT team just a flow of the meeting room management and asked them to build the workflow for the company.
SharePoint is positioned to be one of the most chosen workflow platforms these days. Many companies are excited by the powerful capabilities of SharePoint workflow Microsoft has offered. With built-in features, you can very quickly create an approval workflow for your organization even the requirements include several rules and conditions. This apparently sounds like every letter you may have read in the Microsoft marketing documentation. Microsoft always ‘hypnotizes’ and does attract people in the business community by its writing.
