|
|
Understanding ActiveX controls and PRPC 
As you use PRPC'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 is named OCXInstaller.zip, available on the Resource Kit in the PRPC distribution media. Using this BAT file, you can install either all the ActiveX controls or only a subset, those needed by application users. See PDN article
25737 How to download all ActiveX controls at once.
The ability to download depends on your Internet Explorer security settings on the Tools > Internet Options > Security panel. Depending on control panel settings, you may see a Security Warning dialog or Windows 7 User Account Control dialog. Click Yes or 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.
If you do not have the needed ActiveX files, the message Browser PlugIn Load Errors appears in red, together with the name of the missing ActiveX control
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.
Firefox, Chrome 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, Chrome, or Safari.
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 PRPC 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, PRPC 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. See open authoring. 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. Requires storing temporary files; see Notes below. 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. Requires storing temporary files; see Notes below. Dependencies:
|
Building applications that require no ActiveX controls
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:
- Copy two standard portal rules WorkManager and WorkUser into an application RuleSet (choosing new names to avoid affecting other applications).
- Open each copied portal rule. On the Options tab, clear the Download user OCX on load of portal ? box. Save the updated portal rules.
- In access groups for workers and managers, reference the new portal rules.
- 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.)
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. Requires storing temporary files; see Notes below. Dependencies: |
prDynamicMenus
|
Dynamic Menus Supports the Application Explorer, the Menu Bar control, 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. |
http://support.microsoft.com/kb/269238These controls are also available, but are used only in special situations.
File |
Description |
FormBuilderOCX
|
Form Builder tool used with Form rules. |
prBatchScanning
|
Batch Scanner Obsolete |
prPegaSingleSignon
|
|
Supports single sign-on processing provided through one technique with - 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 PRPC 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 PRPC 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 PRPC ActiveX controls, and then delete allCONFLICTdirectories. (In some cases, you may need to use a Windows CMD session to see and delete theCONFLICTdirectories.) - Before 2001, Microsoft ActiveX controls were called OLE controls.
|
AJAX, open authoring |
|
About Binary File rules
About Service COM rules How to set up Internet Explorer 7 How to set up Internet Explorer 8 How to set up Internet Explorer 9 |