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.
LepideMigrator for Documents is equipped with a myriad of advanced features for requirement based migration. It helps administrators to move shared data from file servers and public folders (Exchange and Office 365) to SharePoint on-premise and SharePoint online without being hindered by the limits and boundaries of un-aided SharePoint migration.
Leale Solutions Uses DocAve to Migrate Microsoft SharePoint Content for a Medical Center with 4,000 End Users…
In several cases your environment is secured and not accessing the internet and you want to install the workflow manager so in the following steps I am going to explain how to do that so you can install Workflow Manager offline to server(s) not connected to the internet..
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.
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.
