Understanding ActiveX controls and Process Commander

The ability to download depends on your Internet Explorer security settings on the Tools > Internet Options > Security panel. You may see a Security Warning dialog. Click  Install  .

All these controls are signed by Pegasystems.

Some controls depend on hidden downloaded files, not visible in Windows Explorer listings. To see the dependencies, right-click the file name and choose Properties from the menu, and then click the Dependency tab. SR-2175

Do not try to delete the files shown on the Dependency tab, as they support ActiveX operations. When you delete any visible file in the Downloaded Program Files directory, Windows also automatically deletes any dependent files no longer needed and cleans up registry entries. (SR-1077 SR-396)

Depending on the application and the features it uses, application users may need access to as many as seven ActiveX controls.

Firefox and Safari do not support ActiveX controls. Do not provide functions that depend on the ActiveX controls listed here if users will access the application through Firefox or Safari.

In some settings, ActiveX controls from vendors other than Microsoft cannot be downloaded and cannot be installed. To design and deploy an application that requires no Pegasystems Inc. ActiveX controls:

1. Copy two standard portal rules WorkManager and WorkUser into an application RuleSet (choosing new names to avoid affecting other applications).
2. Open each copied portal rule. On the Options tab, clear the Download user OCX on load of portal ? box. Save the updated portal rules.
3. In access groups for workers and managers, reference the new portal rules.
4. In your application design and implementation, exclude capabilities that require any of the six controls above. (For example, some reports available from the User portal include the  Export to Excel   button, which depends on prImportManagerOCX. You can copy and override the standard list view rule, turning off this option.) SR-3228
5. If users have Internet Explorer 6, do not implement user interface features that depend on AJAX. Internet Explorer 6 implements the Microsoft XMLHTTP application programmer interface (API) as an ActiveX control. Process Commander applications that use AJAX technology depend on this API. (This API is available in Internet Explorer 7 even when ActiveX controls are disabled.)

Five additional ActiveX controls support application developers, including creation and updating of rules and testing.

These controls are also available, but are used only in special situations.

• The open authoring facilities (including those for text files, HTML, XML, Excel, Visio, and Word) save temporary files on the user's workstation, or on a local directory that must be dedicated to this user to avoid file name conflicts. To identify the appropriate directory for a temporary file, the open authoring facility first looks on the workstation for a Windows environment variable named TEMP. If this variable is not found, it looks next for a Windows environment variable named TMP. If defined, these variables must identify a private, writable directory with available disk space that is dedicated to the workstation or user. If neither environment variable is found, it attempts to use the directory C:\PegaTemp\, creating this directory if possible. Finally, it attempts to use C:\. If none of these are successful, the open authoring process fails.
• These ActiveX controls are stored as Binary File rules with CAB (cabinet) as the file type, the third key part. Developers can access a Process Commander application as a service through an ActiveX control that they create as part of a Service COM interface.
• In some cases when a user accesses multiple Process Commander systems of different versions from one workstation, conflicts may arise between ActiveX control versions. These conflicts appear as directories named CONFLICT.ZZZZ, where ZZZZ is a number. To address this, log off, delete all the Process Commander ActiveX controls, and then delete all CONFLICT directories. (In some cases, you may need to use a Windows CMD session to see and delete the CONFLICT directories.) SR-1051 SR-3320
• Before 2001, Microsoft ActiveX controls were called OLE controls. REMOVED PRCLASSEXPLORER PER B-12082