Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft Visio 2013 Business Process Diagramming and Validation

You're reading from   Microsoft Visio 2013 Business Process Diagramming and Validation Using Microsoft Visio to visualize business information is a huge aid to comprehension and clarity. Learn how with this practical guide to process diagramming and validation, written as a practical tutorial with sample code and demos.

Arrow left icon
Product type Paperback
Published in Nov 2013
Publisher Packt
ISBN-13 9781782178002
Length 416 pages
Edition 2nd Edition
Languages
Arrow right icon
Toc

Table of Contents (14) Chapters Close

Preface 1. Overview of Process Management in Microsoft Visio 2013 FREE CHAPTER 2. Understanding the Microsoft Visio Object Model 3. Understanding the ShapeSheet™ 4. Understanding the Validation API 5. Developing a Validation API Interface 6. Reviewing Validation Rules and Issues 7. Creating Validation Rules 8. Publishing Validation Rules and Diagrams 9. A Worked Example for Data Flow Model Diagrams – Part 1 10. A Worked Example for Data Flow Model Diagrams – Part 2 11. A Worked Example for Data Flow Model Diagrams – Part 3 12. Integrating Validated Diagrams with SharePoint 2013 and Office365 Index

Exporting rulesets to XML

Even though there is an option to import a ruleset from another Visio document, I know that some rules developers would like to export and import rulesets to XML. This allows rulesets to be stored, restored, and analysed more easily.

I decided that the XML structure exported should be the same as the Visio 2013 XML format, and thus use a part of the Visio XML schema. This means using the same namespaces, but it would mean that any XSL stylesheets developed for our export would also work for the validation.xml files found within the zip files that are standard Visio 2013 XML format (*.vsdx and *.vstx files).

I decided to include the option to export the issues in a document, too, because someone may have the need to use them in an external program. Having the issues available in XML format means that they could be displayed as a table, for example, so that they can be reviewed independently.

The ExportDocument() method first constructs a title for SaveFile dialog,...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime