...building hybrid clouds that can support any device from anywhere
Some of you may be using the Orchestrator Visio and Word Generator today, to document your Orchestrator Runbooks. Some of you may also be using the SMART Runbook Conversion Helper, to help understand what your existring Orchestrator Runbooks would look like in Service Management automation (SMA). Understanding that both tools are being used by Orchestrator users, and that they both deal with an “export” capability to either Visio, Word, or PowerShell Workflows, it just made sense to merge the two.
So today I am releasing the SMART Documentation and Conversion Helper 2.0. Still fully written in PowerShell and based on the SMART Runbook Conversion Helper, this tool allows to:
Here is a screenshot of the updated user interface:
Note: As a prerequisite if you plan to use the Visio and Word exports, it is important to go through the image export process. This leverages a separate script also provided with the tool (SMART-DocumentationConversionHelper-ImageExport.ps1), more details can be found in the documentation file included in the download package.
These remain largely the same as the previous versions of the separate tools, and you can refer to the blog posts previously mentioned, as well as to the readme file included with the tool. Only change is related to Visio and Word export:
Detailed requirements are in the readme file in the download package, but in a nutshell you will need a 64-bit machine with PowerShell 4.0 to run the tool, with Visio 2013 and Word 2013 if you wish to leverage this type of export.
Details on the different options in the user interface:
Note : Options for Visio, Word and PowerShell are only available after checking the corresponding export box. For example, you will not be able to choose “Save and Close” for Word, if you have not select the “Export to Word” option.
When doing a PowerShell export, what is the difference between “Skeleton export” vs “Full export”?
These should be the same as what you had in previous versions of the corresponding tools, except for the updated Word export.
PowerShell Export (skeleton mode)
Word Export (extract from the middle of the file)
PowerShell Export (full mode)
The 3 saved exports
PowerShell command output – the Word export is generally the Visio and PowerShell exports are the fastest
This will prove really useful for sure!
I just had a small issue : I couldn't have it connect to a named instance and had to modify the code to remove every mention of the DBPORT from every connection string... I don't really know why .
So, every $Global:SQLConnstr = "Server=" + $Global:DatabaseServer +"," + $Global:DatabasePort + ";Integrated Security=SSPI;database=" + $DatabaseName
need to be changed to $Global:SQLConnstr = "Server=" + $Global:DatabaseServer + ";Integrated Security=SSPI;database=" + $DatabaseName
I have a problem with the SMART Documentation and Conversion Helper.
When I export a Runbook to a Wordfile, it generates some activities twiec or more times.
And also it generates activities from old versions of the runbook. So that means that I have a realy large Wordfile with every activitie in it when ever I had checked out the runbook.
Is there any help for this?
Or someone with the same problem?
I can confirm the behavior that Patrick is seeing with Word exports created via the tool containing all Activities ever associated with a runbook, even if they have been removed from the Runbook Designer Workflow.
For example, I originally had a Query XML activity as part of a runbook being developed, but instead settled on using XPATH queries via a PowerShell script, so I removed the Query XML activity. When I run the SMART tool though, my Word File export contains
references to the original Query XML activity.
It looks like this data might be coming from cached info on the Runbook Server, as I see no reference to my deleted activities in the [Microsoft.SystemCenter.Orchestrator].[Activities] view in the DB.
Found the solution to Issue that Patrick and I were seeing, with deleted activities showing up in the Word Document export.
Line 1119 in SMART-DocumentationConversionHelper.ps1 modified to:
$SqlQueryDOC = "select UniqueID, ObjectType, Name, Description, PositionX, PositionY from OBJECTS WHERE ParentID = '" + $RunbookID + "' AND ObjectType <> '7A65BD17-9532-4D07-A6DA-E0F89FA0203E' AND Deleted = 0"
Hi Lucas and Patrick., and apologies for the late reply.
Thanks Lucas, great find! You are right, this is the SQL Query as it should be on line 1119 - it was correct in the Visio Export routine (line 937) and this was probably an oversight when taking the code from the previous tool and porting it to PowerShell (because
this was some of the things that were supposed to be enhanced along the way!). It is true that deleted activities remain in the Orchestrator DB and need to be filtered out in queries.
Have a great week-end