• Save
Mai Omar Desouki - What's new in SharePoint Designer 2013 #ESPC 2013
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Mai Omar Desouki - What's new in SharePoint Designer 2013 #ESPC 2013

  • 2,779 views
Uploaded on

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
2,779
On Slideshare
2,776
From Embeds
3
Number of Embeds
1

Actions

Shares
Downloads
0
Comments
3
Likes
2

Embeds 3

http://www.linkedin.com 3

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • Advanced users and developers alike can rapidly create SharePoint solutions in response to business needs.Advanced users can compose no-code solutions from collaborative sites and web publishing to Line-of-business data integration, Business intelligence solutions, And human workflows, Leveraging the building blocks available in SharePoint in an easy to use environment. In addition, developers can use SharePoint Designer 2013 to get a quick start on SharePoint development projects.
  • Enables SharePoint 2010 workflow to work in 2013,Execution engine hosted in 2013,InvokeSharePointWorkflow activity send a specific SharePoint’s workflow web service control endpointSome actions from SharePoint 2010 workflows are available in SharePoint 2013 only when using the SharePoint workflow interop.Negotiates between the two execution enginesWF in SharePoint 2010AWS in SharePoint 2013
  • Demo onwfintrop bridge
  • No way to parameterize the different actions within Visio.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 changedNo way to show/use custom actions within VisioAll of these limitations are now gone, and added a bunch of new features to really make this feature shine.
  • Improved visual designerIntegrated the Visio designer into SharePointCan switch between visual designer & sentence styleEditable properties styleDesigner supports (cut / copy / paste / undo / redo / select-all)Declarative workflowsCan call REST/SOAP servicesDynamic Value Data TypeStages & LoopsWorkflows & AppsImproved email editor (rich formatting)
  • http://blogs.msdn.com/b/sharepointdesigner/archive/2012/10/22/introducing-the-new-visual-designer.aspxA whole new workflow design surface.
  • Install SharePoint Designer 2013 & Visio Professional on the same machineThe Visual Designer will not work in any previous versions of SPDOnly Visio Pro will enable the Visual DesignerConnect SPD 2013 up to a SharePoint 2013 site that has the Workflow Manager setupThe Visual Designer will not work on 2010 sitesThis is because you can’t create SharePoint 2013 workflows on SharePoint 2010 sitesCreate a new SharePoint 2013 workflowThe Visual Designer will only work when creating / editing SharePoint 2013 workflowsYou cannot use this feature to create / edit SharePoint 2010 workflows
  • Able to create workflows using click and drag just like in Visio.All of your actions are made available in the left stencil pane.The Stencil pane automatically displays only the list of actions that are appropriate for the type of workflow you are creating.Custom actions will also appear in the stencil.The pane is presorted in alphabetical order.
  • There is no support for Undo (Ctrl-Z).You cannot select multiple objects by clicking and draggingYou cannot move selected items by clicking and dragging objectsShift+Left Mouse Click can be used for multi-selection of actions but it cannot be used to select multiple constructs such as Stage, Step, or Parallel Block.If you try to copy-paste contents across Remote Desktop, it won’t work as we don’t support copy-paste across SPDs with different PIDsCopy-and-paste of workflow actions in the text based designer is not fully integrated with the Clipboard so the ‘Paste’ button within the Clipboard will not work properlyThe ‘Build Dictionary’ action does not keep its properties after being pastedWe also don’t support copy-and-paste across the different workflow platform types. If you try it, you will see one of following messages [demo]
  • Demo about visual designer
  • http://blogs.msdn.com/b/sharepointdesigner/archive/2012/08/10/copy-and-paste-support-in-sharepoint-designer-2013.aspxHow about SharePoint 2010 Workflow type?We also support copy-and-paste for SharePoint 2010 Workflow type (aka. WF3.5 type). Basically the UX will be identical whether you use WF4 workflow or WF3.5 workflow in SPD.Let’s say you have the following workflow that only handles ‘Approved’ status.After you insert an ‘else’ branch and select the two actions highlighted in blue, you can paste them right into the ‘else’ section.It will result in the following logic.Note: I updated the properties of the final action to reflect the proper ‘rejected’ status.How about actions which contains lookup values to other list when they are pasted to a different site without that list?Let’s use this example. If you paste actions which look up values in another list onto a different server, the following will happen.Figure 1. Actions in the source serverFigure 2. Actions in the target serverIf you press the ‘Check for Errors’ or ‘Publish’ button, SPD will indicate that there’s no errors, but the workflow will fail at runtime.So please make sure that you clean up the look ups and update it appropriately after pasting it into a different site.How about actions which are not allowed in the target workflow/area?Let’s say you want to copy an action which is only meaningful in a list workflow and paste it into a site workflow. You will then see the following error or validation error when the ‘Check for Errors’ or ‘Publish’ button is pressed.

Transcript

  • 1. What’s new in SharePoint Designer 2013 Mai Omar Desouki Senior SharePoint Consultant Infusion
  • 2. 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
  • 3. Agenda• Introduction• AWS• Workflow Interop Bridge – Workflow Interop Bridge WF Actions• Workflow Manager 1.0• SharePoint 2010 vs. 2013 Workflows• Workflow Enhancements• Improved Visual Designer• SPD 2010 Limitations
  • 4. 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.
  • 5. 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].
  • 6. 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
  • 7. 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
  • 8. 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)
  • 9. 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.
  • 10. 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 ..
  • 11. 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
  • 12. 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
  • 13. 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)
  • 14. Improved visual designer
  • 15. 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.
  • 16. 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.
  • 17. 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
  • 18. 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
  • 19. 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?
  • 20. 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.
  • 21. Improved E-mail Editor• Easier to format workflow email message by using a standard formatting toolbar to the workflow email editor
  • 22. THANK YOU … It was pleasure seeing you  modesouki@infusion.com