Mai Omar Desouki - What's new in SharePoint Designer 2013 #ESPC 2013Presentation Transcript
What’s new in SharePoint Designer 2013 Mai Omar Desouki Senior SharePoint Consultant Infusion
Who am I? An Egyptian working in Dubai Mai Omar Desouki Senior SharePoint Consultant MCT, MCP, MCTS, MCPD, MCITPBlog: http://maiomardesouki.comFaceboook: http://www.facebook.com/modesoukiTwitter: https://twitter.com/MaiOmarDesouki
Introduction• Rapidly create SharePoint solutions,• No-code solutions,• Business intelligence solutions,• And human workflows,• Easy to use the building blocks,• SharePoint Designer 2013 for Developers.
AWS – Azure Workflow Server• Improves stability, scalability & transparency• Leverages AWS o AWS hosts Workflow Foundation v4 (WF4)• Workflow processing moved to AWS o As a Best Practice: should no longer run on the SharePoint farm / servers. o SharePoint farm & WM farm can be on same / diff server. o Microsoft says not supported to have WM in the same SP server [production environments].
Workflow Interop Bridge• Enables SharePoint 2010 workflow to work in 2013,• Execution engine hosted in 2013,• InvokeSharePointWorkflow activity send a specific SharePoint’s workflow web service control endpoint• Some actions from SharePoint 2010 workflows are available in SharePoint 2013 only when using the SharePoint workflow interop.• Negotiates between the two execution engines – WF in SharePoint 2010 – AWS in SharePoint 2013
Workflow action for the interop bridge• Add List Item Permissions • Set Workflow Status• Assign a Form to a Group • Start Approval Process• Assign a To-do Item • Start Custom Task Process• Capture a version of the Document Set • Start Document Set Approval Process• Collect Data from a User • Start Feedback Process• Copy List Item • Undeclare Record• Declare Record• Inherit List Item Parent Permissions Conditions• Lookup Manager of a User • If current item field equals value• Remove List Item Permissions • Check list item permission levels• Replace List Item Permissions • Check list item permissions• Send Document Set to Repository• Set Content Approval Status Blocks• Set Content Approval Status for the Document • Impersonation block
Workflow Manager 1.0• A new Azure service which introduces new capabilities for authoring, hosting and managing workflows• Provides the capability to host workflows in a high scale.• Workflows are authored using a fully declarative model.• Using Microsoft .NET Framework 4.5• Windows Workflow Foundation (WF4.5)
Unfortunately • No more Design view and Split viewReason: Compared to current versions of Internet Explorer, Design view is anolder technology that does not support many new HTML5 and CSS tags.• Some features of the SharePoint 2010 Workflow platform that are dependent on Windows Workflow Foundation 3.0 are deprecated in SharePoint 2013.Reason: SharePoint 2013 introduces a new SharePoint 2013 Workflowplatform that is built upon Windows Workflow Foundation 4.5 and that isintegrated with Workflow Manager 1.0.
Luckily • In SharePoint Designer 2013, you can still create a SharePoint 2010 Workflow and use all of the SharePoint 2010 Workflow features by choosing the SharePoint 2010 Workflow platform.• You can also integrate features from the SharePoint 2010 Workflow platform into the new SharePoint 2013 Workflow platform. Pain Point • Any SPD WF in 2010, needs to be used in SP 2013; you will have to create from scratch ! Let’s talk about workarounds ..
SharePoint 2010 vs. 2013 Workflows• Types of workflows in SharePoint 2013 – SharePoint 2010 Workflow: • Workflow Foundation v3.5 hosted by SharePoint – SharePoint 2013 Workflow: • Azure Workflow Server: Hosted / On-Premises WF v4• SharePoint 2013 includes the workflow host included in SharePoint 2010 – Based on workflow foundation in .NET 3.5 SP1 – Ensures all legacy workflows will continue to run
SPD 2010 limitations• No way to parameterize the different actions within Visio. o You would always have to switch to the Text-Based Designer to set the action parameters.• When exporting from SPD, you had no idea how your diagram might have been changed• No way to show/use custom actions within Visio
Workflow Enhancements• Improved visual designer – Integrated the Visio designer into SharePoint – Can switch between visual designer & sentence style – Editable properties style• Designer supports (cut / copy / paste / select-all)• Declarative workflows• Can call REST/SOAP services• Dynamic Value Data Type• Stages & Loops• Workflows & Apps• Improved email editor (rich formatting)
Improved visual designer
How do I enable the Visual Designer?• Install SPD 2013 & Visio Professional on the same machine – The Visual Designer will not work in any previous versions of SPD.• Connect SPD 2013 to a SP 2013 site that has the Workflow Manager setup,• The Visual Designer will only work when creating / editing SharePoint 2013 workflows.
So what are the key take aways?• Create workflows using click and drag just like in Visio,• All of your actions are made available in theleft stencil pane.• The actions displayed in Stencil pane autoare appropriate for the type of workflow you are creating.• Custom actions will also appear in the stencil.• The pane is presorted in alphabetical order.
Finally .. Copy Paste is working• Hot keys: Ctrl-C, Ctrl-V, or Ctrl-X, or use the Ribbon menu or the context menu of any selected item.• Support multiple-adjacent-selections.• Paste as text.• Also Shift+Left Mouse Click can be used for multi-selection of actions
But these are not supported ..• There is no support for Undo (Ctrl-Z).• You cannot select multiple objects by clicking and dragging• You cannot move selected items by clicking and dragging objects• Copy-paste contents across Remote Desktop not supported.• The ‘Build Dictionary’ action does not keep its properties after being pasted At The End … it is not fully integrated with the “Paste” Clipboard
Are you asking yourself !• How about SharePoint 2010 Workflow type?• How about actions which contains lookup values to other list when they are pasted to a different site without that list?• How about actions which are not allowed in the target workflow?
Declarative workflows• This term means that instead of being authored in code and then compiled into managed assemblies, the workflow is described (literally) in XAML and then executedinterpretively at run time.• The XAML is derived from the workflow building blocks that you manipulate in the Workflow Designer.
Improved E-mail Editor• Easier to format workflow email message by using a standard formatting toolbar to the workflow email editor
THANK YOU … It was pleasure seeing you firstname.lastname@example.org