Orchestrator Visio and Word Generator v1.3

Rating:        Based on 3 ratings
Reviewed:  3 reviews
Downloads: 902
Released: Oct 27, 2011
Updated: Oct 28, 2011 by brunosa
Dev status: Stable Help Icon

Recommended Download

Application Tool and documentation
application, 486K, uploaded Oct 28, 2011 - 902 downloads

Release Notes

This tool was formerly known as the “Opalis VSD Generator”. Version 1.3 adds support for Orchestrator (RC build as of today) and still supports Opalis Integration Server 6.3.

It lets you export an Opalis policies and Orchestrator runbooks as a Visio diagram, amd you can also generate an optional Word file as well.

Components exported as of v1.3 * 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).

Please see the included guide for requirements for Visio, Word and eventual Visual C++ redistributables.
  • Do not hesitate what additional items it would make sense to export in the Visio or Word document!

For more tools and management packs, you can also visit this blog : http://blogs.technet.com/b/yasc/

Reviews for this release

     
Includes deleted activities. I doubt this is currently in development (looks awefully similar to a product sold by Kelverion).
by CodeBeaver on May 8 at 11:47 AM
     
Having serious problems using this integration pack in Orchestrator SP1, the links between activities dosent appera on visio picture. Any1 else had this kinda of problems?
by JereKarhu on Feb 21 at 7:52 AM
     
I would also like it to automatically name the export files with the name of the runbook being exported. In addition I would like it to provide an option to automatically export child runbooks as well and create separate export files for each child runbook.
by vnerdahl on Sep 14, 2012 at 7:23 PM