How to set up Visio

Process Commander uses an ActiveX control to support working with flows in Microsoft Visio. Follow these steps to set up Microsoft Visio to work with Process Commander flows.

Visio Versions

Process Commander V6.1 SP2 operates with Visio 2003 and higher versions (2007, 2010).

Visio 2007 and 2010 on Vista and Windows 7:

When running in one of these configurations, upon clicking the Process Commander Flow Editor icon, you might find that Visio opens in an external application window instead of within the Process Commander flow editor.

The reason is because Microsoft Office 2007 and Office 2010 set the BrowserFlags registry value for products of the Office suite to open files directly within the appropriate Office application and not within an Internet Explorer session. To enable Visio 2007 and Visio 2010 on Vista and Windows 7 to open in the Process Commander Flow Editor, complete the steps found in the Pega Developer Network article PRKB-26031 Troubleshooting: Visio 2007 opens in an external application window, not within the Flow Editor.

Visio macro security settings and Process Commander

When you open a flow rule as a developer, the system uses an ActiveX control named prVisioInterface and downloads it to your system. Because the control contains VBA (Visual Basic for Applications) macros for use by the Process Commander Visio flow editor, Visio treats the download as a potential security issue.

You can control the Visio macro security settings to allow use of the Process Commander Visio flow editor by using one of the following options.

Option 1: Add Pegasystems as a trusted source of Visio XP macros

The following warning may appear when you first open a flow in Visio.

Make the selection for trusting this publisher (source).
This adds Pegasystems Inc. to the Trusted Publishers list. Pegasystems Inc. has digitally signed the Visio macros with a Code Signing (class 3) Digital ID Certificate from VeriSign.
The Enable Macros button becomes available.
Click Enable Macros to start a successful Visio flow editing session.

After making these selections, this dialog box does not appear again in future uses of the Process Commander flow editor.

Option 2. Set Visio macro security to a lower setting

An alternative to adding Pegasystems as a trusted source is to set your Visio macro security to allow for enabling macros with or without notifying you:

In Visio, access the security settings for macros.
The steps to access these security settings are different depending on your version of Visio:
1. In Visio 2003, select Tools> Macros> Security menu item to access the Security dialog box.
2. In Visio 2007 and 2010, go to the Trust Center Settings to access the macro security settings.
Set the Visio Macro security level to give prompting (select Medium or Disable all macros with notification) or to enable without prompting (select Low or Enable all macros).
Click OK .

Notes

If you only edit flow rules created with Visio and have accepted Pegasystems Inc as a trusted source, you can leave the Visio macro setting at High (for Visio 2003) or Disable all macros except digitally signed macros (for Visio 2007/2010).
For more information on Visio security issues, consult the Microsoft TechNet articles about Visio security settings available from Microsoft.com
Visio requires the Microsoft ActiveX file COMDLG32.OCX to be installed. Some older Windows workstations with few installed applications lack this file. If necessary, this file can be downloaded from Microsoft.com. SR-3260VAGUE SR-7393
Visio editing is not possible for Internet Explorer browsers with Microsoft's Windows Rights Management (RMA) add-on. Remove the RMA to edit flow rules with Visio. SR-18159

	ActiveX control
	Troubleshooting Visio

Help System home page Help Home