The "Opalis VSD Generator" lets you export an Opalis policy as a Visio diagram, and optionnaly a Word document describing the activities and their properties/dependencies (*).
Components exported as of v1.2 are :
- Title of the policy
- Activities and their names/thumbnails/description (description is displayed as a callout in the visio diagram, attached to the shape of the activity)
- Links and their names/colors
- Looping and their interval
Thumbnails and activities are grouped in the Visio diagram, for easy manipulation of the diagram before saving the final layout. Grouping and automatic saving can be disabled in the application settings (*).
This has been developed and tested for Visio 2010 and Word 2010. Word export is optional, so the tool can work if Visio is present, but not Word.
(*) These are new features in v1.2:
Actual change log for v1.2, for those using the previous version (v1.01):
- Less restrictions and clearer requirements when exporting images from policies. All IPs shipping with the product should work now.
- Usability enhancements thanks to a separate settings page with additional automatic checks about your configuration:
Is Visio installed or not
Detection of the extensions path while still providing the ability to override the detection (for installations on other volumes than C: for example)
Automatic listing of the databases
Automatic listing of the Visio stencils and callouts for the chosen VSS file, etc.)
Ability to choose the connectors attachments on the Visio objects (e.g. bottom->top or right-> left)
- First version of Word document generation. The idea is to provide a companion document with more details about the policies, instead of piling more data in the Visio diagram itself
More details and instructions are in the associated documentation and also on this blog : http://blogs.technet.com/b/yasc/
UPDATE : I uploaded the source code as well. A few disclaimers/notes on that:
- Please treat this as community and sample code : I am not a "true" developer or part of the Opalis development team, so the code does not match Microsoft official development standards.
- In the spirit of community sharing, I thank you in advance if you can share your enhancements or fixes to the code, so they can benefits other users as well.