Search icon
Subscription
0
Cart icon
Close icon
You have no products in your basket yet
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Microsoft Visio 2013 Business Process Diagramming and Validation - Second Edition

You're reading from  Microsoft Visio 2013 Business Process Diagramming and Validation - Second Edition

Product type Book
Published in Nov 2013
Publisher Packt
ISBN-13 9781782178002
Pages 416 pages
Edition 2nd Edition
Languages
Author (1):
David Parker David Parker
Profile icon David Parker

Table of Contents (14) Chapters

Preface 1. Overview of Process Management in Microsoft Visio 2013 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

Creating the Rules Explorer window

The Rules Explorer Window is a Visio anchor window, of which there are many examples available, including some in the Microsoft Visio 2013 SDK. The resultant window is a sub-window of the document window, just as with a number of other built-in windows such as the Drawing Explorer, Shape Data window and, of course, the new Issues window. These windows can float free, anchored to an edge of the drawing window or merged with other sub-windows.

The following screenshot of Visual Studio 2012 shows that the FormExplorer class merely acts as a host for the UserControlExplorer control:

The UserControlExplorer control is the WPF control that contains all of the goodies and some code behind. The next image of the Visual Studio 2012 UI shows the UserControlExplorer.xaml file:

The Document Outline shows that very little is defined directly within the TreeViewMain element because it calls on templates defined in Resources.

Self-describing tree views

We wanted the tree...

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 €14.99/month. Cancel anytime}