In my book, Microsoft Visio 2010 Business Process Diagramming and Validation (see http://www.visiorules.com/ ), I presented a table of the progressive maturity of BPM within Visio. I have now extended this diagram in the figure below to show how Visio 2013 increases this maturity level.
I have just been running 2 day Visio 2013 Services introductory courses to Microsoft partners in Oslo and Copenhagen, and I think there has been a very positive response to the new capabilities of Visio 2013 along with SharePoint 2013. The two products together provide some great capabilities that should lead to exciting value propositions to business. New features include co-authoring of Visio files; commenting with or without the Visio client application; deeper integration with SharePoint Designer for SharePoint Workflows; and rendering of Visio files in high quality images, making them usable from any browser on any device.
Microsoft have also merged Visio Premium into Visio Professional for the 2013 product, making all of these features available to the normal business user. The good news about my book mentioned above is that it is very current for Visio 2013 Professional, as there have been no significant changes in this area …
Update : Just got my latest copy of Redmond Magazine ( see http://redmondmag.com/ ). Great article about SharePoint 2013 and Visio 2013!
Kim Laursen says
Thanks for sharing.
Fun to find you have been in Copenhagen.
Should you ever be here again, let me know if you would like to see some of the town with a Danish Visio enthusiast by your side ;0)
davidjpp says
Always interested to talk with Visiophiles! I am considering whther to go the European Sharepoint Conference in February … http://www.sharepointeurope.com/conferences/2013
Fabrizio says
Does Visio 2013 Pro natively exports bpmn 2.0 files?
davidjpp says
No, it does not have native support. You have validation, but no export to XPDL ( see http://www.xpdl.org/ ) or BPEL ( see http://en.wikipedia.org/wiki/Business_Process_Execution_Language )
I have previously pointed this put to the product team 🙂