Contents
Workflow, as far as I can tell at this point, is one of the most overhauled functionalities from SharePoint 2010 to SharePoint 2013. The first major difference is that it’s no longer contained within SharePoint. Workflow is now handled by Windows Azure Workflow (WAW). You can host WAW on-premises just like SharePoint.
Conceptually,SharePoint workflows are used to automate and simplify different work processes, such as document approval, user permission management, reports generating, and many other specific business processes and recurrent daily tasks.
What’s the difference between assign a task and start a task process?
If you have created SPD2013 workflows, you may have noticed that the ‘Assign a Task’ action returns the Task ID. You also may or may have noticed that in 2013, there is also an action called ‘Start a Task Process.’ Let’s take a look at the main differences between these 2 types of actions:
How to start a task process in SharePoint Designer 2013?
As discussed initially a list is Custom List is created as “LeaveApproval”. In this LeaveAproval list, we have taken three columns as LeaveApprover, Leavedatefrom, Leavedateto Open SharePoint designer 2013 then click on “Open Site” from top left and pass the site URL to Open the SharePoint Site under which you will be working.
When to use start a task process workflow?
Start a task process workflow is used to assign a task to multiple participants, whereas Assign a task workflow is assigned to a single participant. You can learn more about Assign a task SharePoint designer 2013 workflow action.
Using Task Actions in SharePoint. A business process often consists of tasks that must be performed by people. A workflow orchestrates the steps of a process. A workflow uses Task Actions to assign tasks to people. For example, when a new employee is hired a number of tasks need to be performed.