![\"Visio's](\"https:\/\/www.microsoft.com\/en-us\/microsoft-365\/blog\/wp-content\/uploads\/sites\/2\/migrated-images\/40\/8117.image1.png\" "\\"SharePoint")
Visualizing processes is at the heart of Visio’s DNA and in Visio 2010 we took a big step forward in that area by including support for SharePoint workflows. This lets users create a workflow in Visio, import it into SharePoint Designer, and make it an executable workflow on SharePoint. In the new Visio we’ve added SharePoint 2013 workflows and made SharePoint Designer an even more integral part of creating workflows visually.<\/p>\n\n\n\n
If you’re not familiar with SharePoint workflows, they are process flows that use pre-defined common activities (such as send email) that can be executed as an automated process on a SharePoint server. This workflow could represent any of a number of business processes, such as a credit approval process, document review feedback, document approval, etc. In Visio 2010 we added a template that would allow you to design a workflow visually, then export your workflow to SharePoint Designer, where you could add parameters to your workflow and publish it.<\/p>\n\n\n\n
The new Visio still includes SharePoint 2010 workflows that you can use as you have in the past, but it also adds the new Microsoft SharePoint 2013 Workflow template.<\/p>\n\n\n\n
Once you create a new SharePoint 2013 workflow, instead of a blank canvas you’ll see that every new workflow starts with an empty container called a “stage<\/em>“. Support for stages was a highly requested feature that allows you to simplify complex workflows. Each stage contains all of the actions that make up that logical section of the workflow. Simple workflows might be only a single stage, while complex workflows could have many stages. Within stages, “step” containers allow you to further organize actions. While all actions must be within a stage, decision shapes can determine the flow both within and between stages.<\/p>\n\n\n\n <\/p>\n\n\n\n With Visio open, if you look at the stencil pane at the left, you’ll see all new shapes. These are not just a visual update; SharePoint 2013 workflow actions and conditions have been updated to support .Net 4.0 workflows. We’ve also added a new stencil, called Components<\/strong>, where you’ll see the shapes to support stages and steps as well as loops<\/strong>, another new highly requested feature.<\/p>\n\n\n\n Along with adding new workflow elements, we’ve eliminated the export step to save workflow for use in SharePoint Designer. SharePoint 2013 workflows you have saved as new Visio Drawing (VSDX) files can be opened in either Visio or SharePoint Designer with no export step needed.<\/p>\n\n\n\n Let’s take a look at how this all works together.<\/p>\n\n\n\n Imagine that your team wants to create a workflow to track credit approvals of your customers. As a first step you decide to rough out the high-level process. To make this easier, after creating your new workflow you first go to the Process<\/strong> tab and click Stage View<\/strong> on the SharePoint Workflow section. It creates a Default Stage View page that uses Simple Stage<\/strong> shapes to represent each stage. Since you hadn’t added any additional stages, all you have is a single, unnamed stage, which looks like this:<\/p>\n\n\n\n <\/p>\n\n\n\n Now you can add additional Simple Stage shapes and Conditions to flesh out your workflow until you have the overall flow of the workflow designed. Then, by selecting the shapes and typing, you can edit the names to reflect the actual stage and condition names and add “Yes<\/em>” and “No<\/em>” labels to the decision branches. When you’re done, it looks more like:<\/p>\n\n\n\n <\/p>\n\n\n\n If it’s a complex workflow, at this point you would probably want to review the workflow with your team, so you could use the new collaboration features to get feedback on the workflow and make sure you have correctly defined the major stages.<\/p>\n\n\n\n Once you’re sure that the diagram is as you want it, you can go back to the Process tab and click Create Workflow<\/strong> and Visio builds you a diagram where empty stage containers replace your stage view shapes, which gives you a framework for your workflow.<\/p>\n\n\n\n <\/p>\n\n\n\n Now you’ll need to add details each stage by adding the proper workflow actions and conditions.<\/p>\n\n\n\n If you look at the Actions<\/strong> stencil you’ll see a lot of different possible actions, such as “Send an email<\/strong>” and “Create list item<\/strong>“. Each of these actions represent an action that can be part of the steps that are executed on the SharePoint server when the workflow is running. You can combine these actions to determine what happens in each stage of your workflow. Let’s focus in on one of the simpler stages, the bankruptcy check to see how building a stage works.<\/p>\n\n\n\n Since our stage view had the names of each of the stages, the generated workflow already has a stage called “Bankruptcy check<\/em>“. We can zoom in on that stage to make our work simpler. The first step we want is to assign a task to the person who will do the research into possible bankruptcies. This is as simple as dragging the “Assign a task” shape onto the stage and dropping it on the line you see running across the stage. Connector splitting will break the connector where you dropped the shape and reattach connectors on each side.<\/p>\n\n\n\n <\/p>\n\n\n\n You can then rename the action so that it’s more meaningful. The bankruptcy check has several other steps in it, including a condition that changes the execution of the workflow depending on whether there has been a bankruptcy or not. You simply add the additional shapes to reflect the flow of the decision, add the names, add labels to indicate which decision connector is “Yes<\/em>” and which is “No<\/em>“, and you’re done. You’ll end up with a stage that looks like this:<\/p>\n\n\n\n <\/p>\n\n\n\n Hint:<\/b> If you design your workflow so that “Yes<\/em>” decisions go to the right and “No<\/em>” decisions go down, your diagram will be more consistent and Visio’s routing engine will do a better job whenever automatic layout occurs.<\/p>\n\n\n\n Once you’ve filled out the entire workflow, used collaboration to get comments and make any adjustments, and you have a workflow that you all agree properly models the steps you want your SharePoint workflow to execute, then you can make the workflow executable. For that you use SharePoint Designer.<\/p>\n\n\n\n In Visio 2010, workflows had to be exported using an intermediate file format that was used only to interoperate with SharePoint Designer. Once the file was opened in SharePoint Designer, adding parameters was a matter of editing text in a programming interface. We’ve simplified both steps in this version.<\/p>\n\n\n\n Since there’s no export step, you simply need to open your saved workflow in SharePoint Designer; Visio’s new Visio Drawing (VSDX) file format lets you move seamlessly between Visio and SharePoint Designer.<\/p>\n\n\n\n SharePoint Designer also now hosts Visio as an ActiveX control, which lets you use the familiar Visio interface to visually edit workflows in SharePoint Designer and add parameters using action tag dialogs if both the new SharePoint Designer and the new Visio are installed on your computer.<\/p>\n\n\n\n First you use the action tag dropdown to select the action you want:<\/p>\n\n\n\n <\/p>\n\n\n\n Then you set the properties using the Action Designer<\/strong> by filling out the appropriate fields in the dialog.<\/p>\n\n\n\n <\/p>\n\n\n\n After you do this for each of the actions, you can then set the conditions for each of the decision shapes:<\/p>\n\n\n\n <\/p>\n\n\n\n When you’re done, the finished workflow can be published so that it will run on the SharePoint Server.<\/p>\n\n\n\n The new Visio lets you design a SharePoint 2013 workflow from an outline to a finished diagram using simple drag and drop and basic editing. You can share and collaborate on the diagram to work with your team to perfect and finalize the workflow. Since SharePoint Designer now supports visual design using the Visio diagramming engine, editing and parameterizing can now be done with a visual interface.<\/p>\n\n\n\n As always, we’d love to hear your comments about this and other posts right here on the blog site, and we encourage you to discuss the new Visio on our forums, Visio Answers<\/a> and the Visio MSDN forum.<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Visualizing processes is at the heart of Visio’s DNA and in Visio 2010 we took a big step forward in that area by including support for SharePoint workflows. This lets users create a workflow in Visio, import it into SharePoint Designer, and make it an executable workflow on SharePoint. In the new Visio we’ve added SharePoint 2013 workflows and made SharePoint Designer an even more integral part of creating workflows visually.<\/p>\n","protected":false},"author":48,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ep_exclude_from_search":false,"_classifai_error":"","footnotes":""},"content-type":[4035],"product":[4036,4066,4072],"audience":[4081],"tags":[],"coauthors":[4862],"class_list":["post-781","post","type-post","status-publish","format-standard","hentry","content-type-tips-and-guides","product-microsoft-365","product-sharepoint","product-visio","audience-enterprise","review-flag-4-1680288349-750","review-flag-alway-1680288348-694","review-flag-etc","review-flag-inter-1680288347-496","review-flag-new-1680288347-871"],"yoast_head":"\n![\"A](\"https:\/\/www.microsoft.com\/en-us\/microsoft-365\/blog\/wp-content\/uploads\/sites\/2\/migrated-images\/40\/0486.image2.png\" "\\"A")
<\/figure>\n\n\n\nAn example of creating a workflow<\/h2>\n\n\n\n
![\"SharePoint](\"https:\/\/www.microsoft.com\/en-us\/microsoft-365\/blog\/wp-content\/uploads\/sites\/2\/migrated-images\/40\/6862.image3.png\" "\\"Simple")
<\/figure>\n\n\n\n![\"A](\"https:\/\/www.microsoft.com\/en-us\/microsoft-365\/blog\/wp-content\/uploads\/sites\/2\/migrated-images\/40\/2313.image4.png\" "\\"SharePoint")
<\/figure>\n\n\n\n![\"An](\"https:\/\/www.microsoft.com\/en-us\/microsoft-365\/blog\/wp-content\/uploads\/sites\/2\/migrated-images\/40\/4338.image5.png\" "\\"Blank")
<\/figure>\n\n\n\n![\"Adding](\"https:\/\/www.microsoft.com\/en-us\/microsoft-365\/blog\/wp-content\/uploads\/sites\/2\/migrated-images\/40\/3264.image6.png\" "\\"Adding")
<\/figure>\n\n\n\n![\"A](\"https:\/\/www.microsoft.com\/en-us\/microsoft-365\/blog\/wp-content\/uploads\/sites\/2\/migrated-images\/40\/6305.image7.png\" "\\"A")
<\/figure>\n\n\n\n![\"Action](\"https:\/\/www.microsoft.com\/en-us\/microsoft-365\/blog\/wp-content\/uploads\/sites\/2\/migrated-images\/40\/2677.image8.png\" "\\"Action")
<\/figure>\n\n\n\n![\"Action](\"https:\/\/www.microsoft.com\/en-us\/microsoft-365\/blog\/wp-content\/uploads\/sites\/2\/migrated-images\/40\/1452.image9.png\" "\\"Action")
<\/figure>\n\n\n\n![\"Setting](\"https:\/\/www.microsoft.com\/en-us\/microsoft-365\/blog\/wp-content\/uploads\/sites\/2\/migrated-images\/40\/8244.image10.png\" "\\"Setting")
<\/figure>\n\n\n\nIn summary<\/h2>\n\n\n\n
Contact us<\/h2>\n\n\n\n