Skip to main content

Mighty SharePoint 2010 Workflows - Part 1 - Using Visio 2010 to create workflows

Because I love automating workflows with SharePoint I have done the following scenario:

1. We have a simple workflow
2. When the item is created on the list we check the item field and if it has specific value send email to someone to approve our item and assign item to approve
3. Then we wait for the item to be changed by approver
4. Finish workflow

Idea was to try new features of Visio 2010 and SharePoint 2010.

OK, let's begin.

1. Start Visio 2010 and choose Flowchart template of diagram on the following nice screen:



2. Select Microsoft SharePoint Workflow and hit Create button:



3. You should see the following screen:



You can see the following Workflow Actions you can choose from:



and Workflow Conditions:



4. Using those shapes create a diagram for the process we have:



5. There is a nother nice option here - Check Diagram - and of course I used it to check my diagram:



6. There were no erros in my case and I exported my diagram into the Workflow.vwi file:





Cool. Next step will be to import my workflow model into SharePoint 2010 to use.

Mighty SharePoint 2010 Workflows - Part 2 - Using SharePoint Designer 2010 to manage workflows

Stay tuned for the rest of the process which will come soon with the next article.


Comments

Popular posts from this blog

Setting up External Content Type for SQL Server database using SQL Server authentication - SharePoint 2010 Foundation

This post is a follow up on the issues that I have got setting up External Content Type (ECT) on SharePoint 2010 Foundation that was going to connect to remote SQL Server database for information. I cannot use my SharePoint user accounts to access SQL Server. According to the information I have discovered ECT and Business Connectivity Services are available in the SharePoint 2010 Foundation, but there are some issues if you want to use authentication methods in your external connections that are different from Windows Identity or Current User Identity. This is because there is no Secure Store Service in SharePoint 2010 Foundation which serves as an impersonation hub and is only available in SharePoint 2010 Server edition. The issues are coming from the fact that you can actually create ECT in SharePoint Designer 2010 providing just Secure Store ID and system would ask you for credentials and here you go, but when you try to use your ECT in External Lists or as a lookup columns you w...

SharePoint 2013 Development and Consulting - Laptop & Conferencing Experience with Lync

Have just jumped on a brand new SharePoint 2013 massive Intranet project and because of specific working conditions have found some items that required addressing almost immediately in order to continue the job. Maybe this will be interesting to someone else who is about to start SharePoint 2013 development to have an idea of what might be necessary. I started working with SharePoint using my own infrastructure in 2009. I used iMac with 320GB HDD and 4GB RAM running VMWare Fusion to virtualise Windows  environment ( SQL Server 2008, standalone SharePoint 2007, Visual Studio 2008, Office 2007). It was all-in-one virtual machine. A bit slow, but enough for any SharePoint work that I had at that time. For communication with colleagues and partners we used GoToMeeting . Great tool that worked (and still works) without any problems. Voice, video, screen-sharing - all worked well using built-in audio/video hardware. In 2010 I got a MacBook Pro  with 500GB HDD and 8GB ...

InfoPath 2013 Preview - URL not valid error when publishing

In InfoPath 2010 there is a problem when you try to publish a Form to a SharePoint site that doesn't have root site collection. You will get an error message "The following url is not valid". It's described here:   http://support.microsoft.com/kb/981854 The solution is to create root site collection for the Web application. Same problem is with InfoPath 2013: In my situation I didn't create the root site collection initially, but used "/sites" managed path instead for all site collections. To solve the problem with InfoPath I had to create it. Used a new site template "Project Site". Will get a chance to research that too. :)