Understanding
ActiveX controls and Process Commander
|
|
As you use Process Commander's portal interface, Internet Explorer may automatically download Microsoft ActiveX controls (also known as OCX files) to support special functions.
These are
downloaded as needed into the Downloaded Program Files
directory.
If preferred, you can download the ActiveX controls all at once
using an installer BAT file. This file and instraucnamed OCXInstaller.zip,
available on the Resource Kit in the Process Commander
distribution media. Using this BAT file, you
can install either all the ActiveX controls or only a subset, those
needed by application users.
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.
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.
ActiveX controls for application users
Depending on the application and the features it uses, application users may need access to as many as seven ActiveX controls.
File |
Name and description |
||||||||||||||||||||||||
PegaImgViewer
|
Image Viewer Supports the Image Viewer tool used for scanning, manipulating, and viewing scanned attachments. See Using the Image Viewer. Dependencies:
|
||||||||||||||||||||||||
PegaOutlookAddInCaller
|
Enables Process Commander applications to communicate
with an operator's Microsoft Outlook calendar. Used
only if application developers include the Get
Appointment List or Send Meeting
Request flow actions in the application. Then, the
first time an operator uses either flow action, Process
Commander uses the |
||||||||||||||||||||||||
prKeyUtils
|
Key Utility Keyboard utility routines. Dependencies: |
||||||||||||||||||||||||
prOpenAuthoring
|
Open Authoring Supports dispatching of Microsoft Word, HTML, Java, and XML editors. Supports conversion of Word DOC files to PDF form. Required for application users if they edit Word attachments or correspondence, or convert Word DOC files to PDF format using the Amyuni Technologies print driver. Used by all developers. See open authoring. Dependencies:
|
||||||||||||||||||||||||
prScreenCapture
|
Screen Capture Supports user's ability to take screen shot attachments. See screen shot attachment. Dependencies:
|
||||||||||||||||||||||||
prVisioInterface
|
Visio Flow Editor Embedded Supports access to Microsoft Visio from the Flow form, and inline Word display. Dependencies:
|
Building applications that require no ActiveX controls
Five additional ActiveX controls support application developers, including creation and updating of rules and testing.
File |
Description |
PegaClientSupport
|
Client-Side Utilities Supports saving trace details in the Performance tool and Tracer tool. Dependencies: |
prDeveloper
|
Same contents as |
prImportManagerOCX
|
Excel Data Import Manager Supports the use of Excel in editing Data Tables with the Data Table editor. Needed by users only if they edit Data Tables or use the Edit In Excel feature in list view reports. Not needed to export reports to Excel. Dependencies: |
prDynamicMenus
|
Dynamic Menus Supports the Application Explorer and menus used in some portal rules. Dependencies: Also requires that Microsoft's XML Parser MSXML.dll be installed. (This DLL has many versions; a version normally installed with many Microsoft layered products such as Office. See |
|
|
Com Interface Supports development of Microsoft Component Object Model (COM) objects, in conjunction with Visual Basic and Service COM rules. |
These controls are also available, but are used only in special situations.
File |
Description |
FormBuilderOCX
|
Form Builder tool used with Form rules. |
prBatchScanning
|
Batch Scanner Supports an older scanner interface for automatic scanning. See About the Scan Station. Used with Windows 2000; not supported for Windows XP. Dependencies: |
prPegaSingleSignon
|
|
PRKB-25292 Integrating with Outlook
calendars.
http://support.microsoft.com/kb/269238
Supports single sign-on
processing provided through one technique 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.)
|
AJAX |
|
About
Binary File rules
About Service COM rules How to set up Internet Explorer 6 How to set up Internet Explorer 7 |