I frequently reference two resources linked at the bottom of this post that speak to the features unique to 2010 and 2013 workflows. Unfortunately, once you pick which workflow platform you’ll be building upon you can’t switch. So it’s important to use these lists in your evaluation phase to make sure you’ll be picking the right platform for the job. Keep in mind, you can always start a 2010 workflow from within a 2013 workflow.
Actions Exclusive to 2010
|
New in 2013 Workflows
|
- Actions:
- Stop Workflow
- Capture a Version of the Document Set
-
- Send Document Set to Repository
- Set Content Approval Status for the Document Set
- Start Document Set Approval Process
- Declare Record
- Set Content Approval Status
Undeclare Record
- Add List Item
- Inherit List Item Parent Permissions
- Remove List Item Permissions
- Replace List Item Permissions
- Lookup Manager of a User
- Assign a Form to a Group
- Assign a To-Do Item
- Collect Data from a User
- Start Approval Process
- Start Custom Task Process
- Start Feedback Process
- Copy List Item (SharePoint Designer 2013 supports only the document-copying action.)
- Conditions:
- If current item field equals value
- Check list item permission levels
- Check list item permissions
- Steps:
- Data sources:
- Other features:
- Visio integration
- Association Column
- Content Type Association for reusable workflow
- ‘Require Manage List/Web
- Permission’ feature for list/site workflow
- Globally reusable workflow type
- Workflow visualization option
|
- A visual workflow development experience that uses a Visio 2013 add-in
- A new action that enables no-code web service calls from within a workflow
- New actions for creating a task and starting a task process
- New coordination actions that let you start a workflow built on the SharePoint 2010
- Workflow platform from a workflow built on the SharePoint 2013 Workflow platform
- A new Dictionary type
- New workflow building blocks such as Stage, Loop, and App Step
|
|
|
|
Like this:
Like Loading...
Related
Hi, would be interesting to mention what isn’t in SP2013 Workflow 🙂 Like manage items permissions from SP2013 isnt available compared to SP2010. I generally create a 2010 workflow to manage permission (called from SP2013 workflow).
Thanks, Jeff. The first column in the table is all actions that are not available in 2013, but in 2010.
oh sorry my bad I misunderstood 😀 Perfect then