Visio and Process Navigator can be configured through their user-interfaces, but particularly when deploying Process Navigator to numerous users, making those settings directly to the Registry through a REG file or a script can be quicker and ensure a consistent set-up. We have a template script that requires just a little tweaking to make it applicable to a customer's set-up. Do let us know if that would be of interest.
These are common Visio configurations and their related Registry settings. Note that these are all userspecific, and wouldn't require elevated permissions to apply.
|Drawings||HKCU\Software\Microsoft\Office\<Version>\Visio\Application DrawingsPath (REG_SZ)||Typically, the main location in which maps are stored, e.g. \\TriasterServer\Triaster\TriasterServer2011\MapStore\Process Library\Sandpit Maps|
|Stencils||HKCU\Software\Microsoft\Office\<Version>\Visio\Application StencilPath (REG_SZ)||This could be a shared location on the Triaster Server, e.g. \\TriasterServer\Triaster\TriasterServer2011\MapStore\Stencil, Template and Properties Multiple paths can be specified, separated by semi-colons. The Process Navigator installer will add the 'Templates and Stencils' folder within the Process Navigator installation.|
|Templates||HKCU\Software\Microsoft\Office\<Version>\Visio\Application TemplatePath (REG_SZ)||This would be the same location as for stencils.|
|Default format - SaveVisio files as Save documents - Save files in this format||HKCU\Software\Microsoft\Office\<Version>\Visio\Application SaveFileFormat (REG_SZ)||The Visio XML Document (VDX) format is required by Process Navigator. SaveFileFormat = 2|
Visio 2007: Tools > Trust Center > Macro Settings
Visio 2010: File > Options > Trust Center > Trust Center Settings... > Macro Settings
|Security Level Macro Settings||HKCU\Software\Microsoft\Office\<Version>\Security Level (REG_DWORD) (Visio 2003) VBAWarnings (REG_DWORD) (Visio 2007, 2010)||It's important that Visio on a Triaster Server does not prompt with macro warnings, as that would stall an automated, noninteractive publication. On a server, we recommend macro warnings are set to the lowest level. Level = 1 (Visio 2003) VBAWarnings = 1 (Visio 2007, 2010)|
|Trust access to the VBA project object model||HKCU\Software\Microsoft\Office\<Version>\Security AccessVBOM (REG_DWORD)||This needs to be enabled. AccessVBOM = 1|
This article is available in more detail from our Knowledge Base, including configurations for Process Navigator, and with a template script.