You are on page 1of 20

What's new in PRPC 7.1.

Mobile

Build, apply branding to, and distribute a hybrid mobile app using
the Mobile Settings tab in Designer Studio. Access your app using
the Pega 7 mobile app, available for download from the Apple
iTunes or Google Play app stores.

The Mobile Mashup SDK integrates with a new or existing Apple iOS
or Android mobile application to provide enhanced functionality and
collaboration between the app and PRPC.

Create a seamless user experience when moving between a


desktop and a mobile application using the Address Map and
Signature Capture controls.

Decision Management

Decision parameters provide the extension and customization points


to provide flexible inputs to the strategy.

The external input mechanism allows you to design reusable


strategies and test strategies with predefined inputs.

Using split and exclusion components, you can build traditional


segmentation trees in strategies.

Iterative components provide cumulative calculations capabilities to


strategies.

Use the features added by the Decision Manager ruleset in PegaDM


to enable business users to own parts of an enterprise application
within the boundaries defined by IT: revision management and
proposition authorization.

Case Management

Stage-related audit notes now appear on the user form's Audit tab.
You can manage which notes appear for a given case.

Attachment step simplifies attaching files and their categories to


cases.

A search field on the Form Configuration dialog lets you locate


specific records from a list returned by a data page.

Geolocation tracking enables you to capture latitude and longitude


information for every requestor action in the audit trail. A Map it
link launches a Google Map that shows where the action occurred.

Process Modeler property panels have been reorganized so that it's


easier to find the fields you're likely to need; for example, the
Assignment shape property panel groups actions, routing, SLA, and
specification fields at top. Instructional labels beneath the fields

describe them in non-technical terms.

Users can uniformly create ad hoc cases using the standard starting
flow pySimpleCaseWorkFlow. The default action contains a
dashboard that also enables operators to quickly define tasks and
add attachments.

Users can easily convert ad hoc cases into a case types that can be
reused throughout the organization employing the Configure for
Reuse feature.

You can associate SLAs with individual flows within a stage-based


process.

Designer Studio

View a customized list of pinned classes in the Application Explorer


without explicitly switching context.

Deprecate rules and classes in your application to steer users away


from unsupported features.

You can now check out and fix an invalidated rule.

Use the centralized Find Rules landing page to pinpoint rules in your
application or system.

Use the UI Tree tool in Designer Studio and at runtime to view the
hierarchy of artifacts on a page.

Project Delivery

Some rules and classes have been deprecated.

Add attachments to requirements using the Application Profile


landing page or Requirement rule form.

Use the Application Document Wizard to generate project artifacts.


Generated documents now include: embedded ERDs, an interactive
Stages and Processes diagram, and all flows without restrictions.

User Interface

Single Document Dynamic Containers are now created with frames


disabled by default.

Read-only fields can be marked as an email, URL, or phone number


in the Read-Only Format settings.

Column Properties include the ability to add a property for sorting


and filtering a column that contains a section include.

Column headings can now be aligned with the column data.

Improvements to dynamic layouts let you specify refresh conditions

and use natural label widths.

The UI Kit ruleset allows you to build or customize responsive user


interfaces with rules and skins based on the latest standard Pega
UI.

Customizable modal templates can be used wherever a modal


dialog is launched.

Stacked layout group lets you stack items in a customizable,


responsive format.

The X-UA-Compatibility meta tag setting can be specified on


harnesses to override IE Compatibility View setting.

Reporting

Reduce the load on the main database by running reports against


the alternate database. The control is on the Data Access tab of the
Report Definition.

Integration

When you create a REST integration, you can create a data page
(and its related data type and data transforms) at the same time.
The data page uses the integration as one of its sources.

Give your users the convenience of single sign-on authentication


with SAML 2.0.

System Management

PRServlet is no longer required in a URL when accessing PRPC. A


URL formerly written like this:

http://example.com/prweb/PRServlet?[QueryString]

The PDN provides overview articles, best-practice solutions to common


development challenges, news of the latest PRPC features, access
to the latest version of the PRPC help docs, and many more
learning resources.
Learn from the experts. Pega Academy courses provide design and
implementation best practices covering PRPC application
development as well as specialized topics.
Pega Academy courses provide you with the knowledge and hands-on
experience you need to successfully design and deploy PRPC
solutions.
These courses also prepare you to become a Pega Certified
Professional.

Designer Studio basics


Designer Studio provides development team members of all technical levels the tools and
information they need to build or extend existing enterprise applications.
The Designer Studio is available to users who are associated with an access group that identifies the
standard portal rule as their current portal.
The following features comprise the Designer Studio:

Area
Header bar

To learn more
The header bar appears at the top and identifies the currently selected
application, supports search, enables you to start processes, create
new rules and applications, and provides quick access to other
information and tools. See:

Using the header and developer toolbar

Using Search

Using the Application menu

Using the Operator menu

Click

to access landing pages. See About Landing

Pages
Work area

The work area in the center of Designer Studio displays rule forms,
instances lists, wizards, landing pages, Home display, or other tools
and forms. You can have multiple items open in the work area. The tab
bar appears at the top of the work area. Labels on the tabs identify the
contents. Click a tab to display it. The active tab is highlighed. Click x
on the tab to close it.
If there are many open tabs, click the Currently Open icon

to

display a list of available tabs and select the one you want. Select Close
All to close all the open tabs (except the Home tab).
You can remove the tabs in the work area by clearing the Include Tabs
checkbox in the Designer Studio Navigation area on the operator
Preferences pop-up dialog.
Developer toolbar

The developer toolbar appears at the bottom and offers advanced


developer tools and menus. It also contains a link to the Pega
Discovery Network and system information. See Designer Studio
Using the header and developer toolbar.

Explorer area

The Explorer area is displayed at the left of the Designer Studio. Click
an Explorer icon to display it.

Recent: Display and access up to 20 recently opened rule or


data instance records, wizard items, instance lists, landing
pages, and cases. See Using the Recent Explorer.

Cases: Presents the case types belonging to your current


application organized in a tree structure indicating parent and
sub-case type relationships. You use this Explorer to open, for
each case type, its Case Designer landing page, which is where
you configure a case type's processes and specifications. See
Using the Cases Explorer.

Data: Presents data object types and the data pages that
are associated with them. You can filter the display by
application or applies-to class. See About the Data Explorer.

App: Display the Application Explorer, which contain


records belonging to RuleSet versions that belong to your
current and built-on applications, organized by class, rule or
data category, rule type, and rule instance. See Using the
Application Explorer.

Records: Presents all rules and data instance records in


your system, organized by category and type. See About the
Records Explorer.

Private: Shows your checked-out records. See About the


Private Explorer.

Favorites : Lists your personal and access group favorites.


See About the Favorites Explorer.

Explorer menu
The heading of each Explorer displays a down-arrow icon

. Click it to

display a menu of actions you can take in the Explorer. Below is an


example of the Recent Explorer menu

All Explorer menus allow you to create rule or data records by clicking
+Create. Select a rule type or data class from a list of rule or data type

class categories.
Home display

The Home display appears by default when you open Designer Studio

and contains the following:

Guardrail Warnings Charts showing warnings created in the

last seven days by you and other operators with access to the
current application.

PDN News Contains a Pega Discovery Network (PDN) RSS

feed that allows you to directly open new articles of special


interest to the developer community. You can also access the
PDN by searching for articles, or clicking a link to access the
PDN Forums. If required, this RSS feed may be disabled using a
dynamic system setting.

Pega Task Displays a near real-time list of tasks that you

and other operators with access to the current application are


working on.

View PMF worklist in new window link Click to display My

Project Worklist, which presents open user stories, tasks, bugs,


and issues currently assigned to you in the Project Management
Framework (PMF). This link appears only if your application is
enabled for PMF connectivity.
See Working with the Home Display.
You can open the Home display by clicking

When you create an application in Application Express, the


Application Overview landing page appears in the Home display.

How to set up Internet Explorer


The Designer Studio and cross browser compatible applications built on PRPC are accessible using
Microsoft Internet Explorer 8, 9, 10, and 11.
Most configuration takes place in the Internet Options window. To display this window, select Tools >
Internet Options.

Browser plug-ins
Certain PRPC features require browser plug-ins. It is recommended that you log out of PRPC and
restart your browser after installation is complete.
Depending on operating system and browser settings, users at workstations with internet access can
download these plug-ins quickly upon first use. If you are not able to successfully download and
install the following plug-ins, contact your system administrator.

Plug-in
Adobe Flash Player

Instructions
Adobe Flash Player (version 9 or higher) is required when using referencing
rules,
the Declarative Network Analyzer and other displays in your application.
Download available at: www.adobe.com/products/flashplayer

Microsoft Silverlight

Microsoft Silverlight is required when using Document Scanner flow actions in


your application.
Download available at: www.microsoft.com/silverlight/

NOTE: If you are using features integrated with Word merge, the
PRPC Silverlight prerequisites file must also be installed. For more details, see
How to support Word merge.

Adobe Reader

If you want to integrate Adobe Reader with an accessible application, see PDN
article Adding browser plug-ins to accessible applications

Pop-up blocker
PRPC requires pop-up windows; ensure your browser has the pop-up blocker disabled. For browsers
that allow exceptions, an alternative is to leave the pop-up blocker enabled but add the nodes hosting
your PRPC application to the list of "allowed" sites.

Using multiple tabs


You can use multiple tabs in your browser to connect to different PRPC systems or to have multiple
connections to a single PRPC system using the same Operator ID.
You cannot use multiple tabs to connect to a single PRPC system with different Operator IDs. All browser
sessions run in a single, common Windows process and share cookies.
To avoid other desktop applications from inadvertently displacing your PRPC session, use the following tips:

Right click on links and select the open in new window or tab option

Configure your browser to explicitly open all links in new window or tab

For Internet Explorer users, ensure the "Reuse windows for launching shortcuts" setting is disabled

In the event that your PRPC session is replaced by another application , use the Back icon to return to your
work and continue. If you close the browser window, your PRPC session (and any unsaved work) will be
lost.
NOTE: You cannot use Outlook Web Access in one tab and a PRPC session in another tab. Logging out of an
Outlook Web Access server clears cookies for all tabs in the same window, ending your PRPC session. All
uncommitted work is lost; log in again to start a new session.

Cookies
PRPC requires persistent cookies. Ensure your browser settings allow cookies. For browsers that allow
exceptions, an alternative is to disable cookies but add the nodes hosting your PRPC application to the list
of "allowed" sites.

ActiveX controls
ActiveX controls are required for a subset of PRPC features to function correctly. These controls are shipped
with PRPC, digitally signed by Pegasystems Inc., and only supported in version of Internet Explorer.
If your Windows network account and browser settings permit downloading, ActiveX controls will
automatically download and install, on demand, when first needed. Typically, Windows stores downloaded
content in the C:\Windows\DownloadedProgramFiles directory.
Under Tools > Internet Options, on the Security tab, confirm that you can download signed ActiveX
controls using the Local intranet zone. You can set security for the Local intranet zone to Low, or can choose
Custom and turn on the download settings:

NOTE: ActiveX controls can be installed individually or as a batch using an installer found on the PRPC
installation media.
If you have issues accepting ActiveX controls, contact your system administrator. For more details on all
ActiveX controls used by PRPC, see Understanding ActiveX controls and PRPC.

Security settings
Typically, the PRPC server operates on a local area network (LAN) and appears in the Local Zone of Internet
Explorer. You can change security settings for the Local Zone without affecting the security settings you
want to apply for the Internet. The default Local Zone security setting of Medium or Medium-Low is
generally appropriate for PRPC use.

NOTE: Most LANs include a domain name server so you can


identify the server hosting PRPC by name. If you use a numeric
IP address in the URL (such as "http://10.1.29.52:80/prweb/")
Internet Explorer applies the security settings in the Internet
Zone, NOT the Local Zone. Internet Zone settings are more
restrictive than the Local Zone and may prevent proper
operation of PRPC. Avoid using an IP address rather than a
domain name. Alternatively, access Tools > Internet Options >
Security > Trusted sites > Sites and add the IP address as a
trusted site.

Restrictions on file downloads


If your PRPC server is identified by an IP address or by a
domain-qualified name (such as myserver.mydomain.sub) in the
browser's address line, you may be prompted before
downloading a file. This can restrict your ability to use file
attachments. To avoid this restriction, ensure your browser has
the "Always prompt before downloading" option disabled.
For Internet Explorer users, specifying HTTPS in your URL may
block certain download operations from the server to
workstations. For details and suggestions, see PDN article Troubleshooting: "Internet Explorer cannot
download" messages (Tomcat with SSL) .

Scripting
PRPC uses JavaScript. Applications may use VBScript in addition to JavaScript. Ensure your browser has
JavaScript enabled.

Cache Settings
Temporary Internet Files
The open authoring facilities (including those for text files, HTML, XML, Excel, and Word) save temporary
files on the user's workstation, or on a local directory that is 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, make sure that these variables 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.
Page refresh settings
PRPC uses HTTP 1.1 and marks pages as expired when appropriate. No exposed method is available that
allows a user to instruct the browser to automatically clear the browser cache when the user refreshes a
page. You can, however, manually clear the cache by reviewing your browser's "history", "browsing data" or
"network" settings.
The system responds best if your browser cache is enabled, because the cache can store images and other
static files locally. Browser caching is not required.

Access to browser clipboard


When editing a section rule, you can cut, copy, and paste cells. This facility uses the browser's own
clipboard, and may produce a warning dialog:

Do you want this webpage to access your Clipboard?

To suppress this warning, in the Local or Trusted Sites zone, select Tools > Internet Options > Security >
Trusted Sites > Custom Level. In the Scripting group, Set the Allow Programmatic clipboard
access to Enable.

Performance tips
Developers and users are most productive if they remember these tips:

Click the Pega logo in the header of the Designer Studio to open the Home Page

Use keyboard shortcuts in conjunction with default browser hot keys

Use the Actions > Refresh action found on all form headers to refresh only the form in focus

Review browser add-ons for any unnecessary entries. Certain non-Microsoft add-ons can
significantly impact performance of the Designer Studio

Do not use the browser refresh hot key F5 when using multiple tabs in a single session

Do not use the browser history capabilities, Back icon or keyboard shortcut to return to an earlier
page; stale information can interfere with PRPC server synchronization

How to set up Chrome for application users


The Designer Studio and cross browser compatible applications built on PRPC are accessible using Google
Chrome version 9 or later.
Most configuration takes place in the Settings tab. To display this tab, select Customize Menu >Settings or
enter "chrome://settings/" in the address bar.

Browser plug-ins
Certain PRPC features require browser plug-ins. It is recommended that you log out of PRPC and restart
your browser after installation is complete.
Depending on operating system and browser settings, users at workstations with internet access can
download these plug-ins quickly upon first use. If you are not able to successfully download and install the
following plug-ins, contact your system administrator.

Plug-in
Adobe Flash Player

Instructions
Adobe Flash Player (version 9 or higher) is required when
using referencing rules,
the Declarative Network Analyzer and other displays in your application.
Download available at: www.adobe.com/products/flashplayer

Microsoft Silverlight

Microsoft Silverlight is required when using Document Scanner flow


actions in your application.
Download available at: www.microsoft.com/silverlight/
NOTE: If you are using features integrated with Word merge, the
PRPC Silverlight prerequisites file must also be installed. For more details,
see How to support Word merge.

Adobe Reader

If you want to integrate Adobe Reader with an accessible application, see


PDN articleAdding browser plug-ins to accessible applications

10

Pop-up blocker
PRPC requires pop-up windows; ensure your browser has the pop-up blocker disabled. For browsers that
allow exceptions, an alternative is to leave the pop-up blocker enabled but add the nodes hosting your PRPC
application to the list of "allowed" sites.

Using multiple tabs


You can use multiple tabs in your browser to connect to different PRPC systems or to have multiple
connections to a single PRPC system using the same Operator ID.
You cannot use multiple tabs to connect to a single PRPC system with different Operator IDs. All browser
sessions run in a single, common Windows process and share cookies.
To avoid other desktop applications from inadvertently displacing your PRPC session, use the following tips:

Right click on links and select the open in new window or tab option

Configure your browser to explicitly open all links in new window or tab

For Internet Explorer users, ensure the "Reuse windows for launching shortcuts" setting is disabled

In the event that your PRPC session is replaced by another application , use the Back icon to return to your
work and continue. If you close the browser window, your PRPC session (and any unsaved work) will be
lost.
NOTE: You cannot use Outlook Web Access in one tab and a PRPC session in another tab. Logging out of an
Outlook Web Access server clears cookies for all tabs in the same window, ending your PRPC session. All
uncommitted work is lost; log in again to start a new session.

Cookies
PRPC requires persistent cookies. Ensure your browser settings allow cookies. For browsers that allow
exceptions, an alternative is to disable cookies but add the nodes hosting your PRPC application to the list
of "allowed" sites.

ActiveX controls not supported


ActiveX controls are only supported in Internet Explorer. Safari, Chrome and Firefox users are unable to use
functions that rely on ActiveX controls. See Understanding ActiveX for more information on how these
controls are used by PRPC.

Restrictions on file downloads


If your PRPC server is identified by an IP address or by a domain-qualified name (such
asmyserver.mydomain.sub) in the browser's address line, you may be prompted before downloading a file.
This can restrict your ability to use file attachments. To avoid this restriction, ensure your browser has the
"Always prompt before downloading" option disabled.

Scripting
PRPC uses JavaScript. Applications may use VBScript in addition to JavaScript. Ensure your browser has
JavaScript enabled.

Cache Settings
Temporary Internet Files
The open authoring facilities (including those for text files, HTML, XML, Excel, and Word) save temporary
files on the user's workstation, or on a local directory that is 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

11

a Windows environment variable named TMP. If defined, make sure that these variables 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.
Page refresh settings
PRPC uses HTTP 1.1 and marks pages as expired when appropriate. No exposed method is available that
allows a user to instruct the browser to automatically clear the browser cache when the user refreshes a
page. You can, however, manually clear the cache by reviewing your browser's "history", "browsing data" or
"network" settings.
The system responds best if your browser cache is enabled, because the cache can store images and other
static files locally. Browser caching is not required.

Performance tips
Developers and users are most productive if they remember these tips:

Click the Pega logo in the header of the Designer Studio to open the Home Page

Use keyboard shortcuts in conjunction with default browser hot keys

Use the Actions > Refresh action found on all form headers to refresh only the form in focus

Review browser add-ons for any unnecessary entries. Certain non-Microsoft add-ons can
significantly impact performance of the Designer Studio

Do not use the browser refresh hot key F5 when using multiple tabs in a single session

Do not use the browser history capabilities, Back icon or keyboard shortcut to return to an earlier
page; stale information can interfere with PRPC server synchronization

How to set up Firefox for application users


The Designer Studio and cross browser compatible applications built on PRPC are accessible using Mozilla
Firefox version 5 or later.
Most configuration takes place in the Options window. To display this window, select Firefox >Options

> Options.

Browser plug-ins
Certain PRPC features require browser plug-ins. It is recommended that you log out of PRPC and restart
your browser after installation is complete.
Depending on operating system and browser settings, users at workstations with internet access can
download these plug-ins quickly upon first use. If you are not able to successfully download and install the
following plug-ins, contact your system administrator.

Plug-in
Adobe Flash Player

Instructions
Adobe Flash Player (version 9 or higher) is required when
using referencing rules,
the Declarative Network Analyzer and other displays in your application.
Download available at: www.adobe.com/products/flashplayer

Microsoft Silverlight

Microsoft Silverlight is required when using Document Scanner flow


actions in your application.

12

Download available at: www.microsoft.com/silverlight/


NOTE: If you are using features integrated with Word merge, the
PRPC Silverlight prerequisites file must also be installed. For more details,
see How to support Word merge.
Adobe Reader

If you want to integrate Adobe Reader with an accessible application, see


PDN articleAdding browser plug-ins to accessible applications

Pop-up blocker
PRPC requires pop-up windows; ensure your browser has the pop-up blocker disabled. For browsers that
allow exceptions, an alternative is to leave the pop-up blocker enabled but add the nodes hosting your PRPC
application to the list of "allowed" sites.

Using multiple tabs


You can use multiple tabs in your browser to connect to different PRPC systems or to have multiple
connections to a single PRPC system using the same Operator ID.
You cannot use multiple tabs to connect to a single PRPC system with different Operator IDs. All browser
sessions run in a single, common Windows process and share cookies.
To avoid other desktop applications from inadvertently displacing your PRPC session, use the following tips:

Right click on links and select the open in new window or tab option

Configure your browser to explicitly open all links in new window or tab

For Internet Explorer users, ensure the "Reuse windows for launching shortcuts" setting is disabled

In the event that your PRPC session is replaced by another application , use the Back icon to return to your
work and continue. If you close the browser window, your PRPC session (and any unsaved work) will be
lost.
NOTE: You cannot use Outlook Web Access in one tab and a PRPC session in another tab. Logging out of an
Outlook Web Access server clears cookies for all tabs in the same window, ending your PRPC session. All
uncommitted work is lost; log in again to start a new session.

Cookies
PRPC requires persistent cookies. Ensure your browser settings allow cookies. For browsers that allow
exceptions, an alternative is to disable cookies but add the nodes hosting your PRPC application to the list
of "allowed" sites.

ActiveX controls not supported


ActiveX controls are only supported in Internet Explorer. Safari, Chrome and Firefox users are unable to use
functions that rely on ActiveX controls. See Understanding ActiveX for more information on how these
controls are used by PRPC.

Restrictions on file downloads


If your PRPC server is identified by an IP address or by a domain-qualified name (such
asmyserver.mydomain.sub) in the browser's address line, you may be prompted before downloading a file.
This can restrict your ability to use file attachments. To avoid this restriction, ensure your browser has the
"Always prompt before downloading" option disabled.

13

Scripting
PRPC uses JavaScript. Applications may use VBScript in addition to JavaScript. Ensure your browser has
JavaScript enabled.

Cache Settings
Temporary Internet Files
The open authoring facilities (including those for text files, HTML, XML, Excel, and Word) save temporary
files on the user's workstation, or on a local directory that is 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, make sure that these variables 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.
Page refresh settings
PRPC uses HTTP 1.1 and marks pages as expired when appropriate. No exposed method is available that
allows a user to instruct the browser to automatically clear the browser cache when the user refreshes a
page. You can, however, manually clear the cache by reviewing your browser's "history", "browsing data" or
"network" settings.
The system responds best if your browser cache is enabled, because the cache can store images and other
static files locally. Browser caching is not required.

Performance tips
Developers and users are most productive if they remember these tips:

Click the Pega logo in the header of the Designer Studio to open the Home Page

Use keyboard shortcuts in conjunction with default browser hot keys

Use the Actions > Refresh action found on all form headers to refresh only the form in focus

Review browser add-ons for any unnecessary entries. Certain non-Microsoft add-ons can
significantly impact performance of the Designer Studio

Do not use the browser refresh hot key F5 when using multiple tabs in a single session

Do not use the browser history capabilities, Back icon or keyboard shortcut to return to an earlier
page; stale information can interfere with PRPC server synchronization

How to set up Safari for application users


The Designer Studio and cross browser compatible applications built on PRPC are accessible using
Apple Safari version 5 or later.
Most configuration takes place in the Safari Preferences window. Use any of three ways to display this
window:
1

If the Safari menu bar is available, choose Window > Preferences...

If the Safari menu bar is not visible, select the Settings icon
the menu that displays, select Preferences...

Using the keyboard, click Ctrl +,

at the top right of the screen. From

14

Browser plug-ins
Certain PRPC features require browser plug-ins. It is recommended that you log out of PRPC and restart
your browser after installation is complete.
Depending on operating system and browser settings, users at workstations with internet access can
download these plug-ins quickly upon first use. If you are not able to successfully download and install the
following plug-ins, contact your system administrator.

Plug-in
Adobe Flash Player

Instructions
Adobe Flash Player (version 9 or higher) is required when
using referencing rules,
the Declarative Network Analyzer and other displays in your application.
Download available at: www.adobe.com/products/flashplayer

Microsoft Silverlight

Microsoft Silverlight is required when using Document Scanner flow


actions in your application.
Download available at: www.microsoft.com/silverlight/
NOTE: If you are using features integrated with Word merge, the
PRPC Silverlight prerequisites file must also be installed. For more details,
see How to support Word merge.

Adobe Reader

If you want to integrate Adobe Reader with an accessible application, see


PDN articleAdding browser plug-ins to accessible applications

Pop-up blocker
PRPC requires pop-up windows; ensure your browser has the pop-up blocker disabled. For browsers that
allow exceptions, an alternative is to leave the pop-up blocker enabled but add the nodes hosting your PRPC
application to the list of "allowed" sites.

Using multiple tabs


You can use multiple tabs in your browser to connect to different PRPC systems or to have multiple
connections to a single PRPC system using the same Operator ID.
You cannot use multiple tabs to connect to a single PRPC system with different Operator IDs. All browser
sessions run in a single, common Windows process and share cookies.
To avoid other desktop applications from inadvertently displacing your PRPC session, use the following tips:

Right click on links and select the open in new window or tab option

Configure your browser to explicitly open all links in new window or tab

For Internet Explorer users, ensure the "Reuse windows for launching shortcuts" setting is disabled

In the event that your PRPC session is replaced by another application , use the Back icon to return to your
work and continue. If you close the browser window, your PRPC session (and any unsaved work) will be
lost.

15

NOTE: You cannot use Outlook Web Access in one tab and a PRPC session in another tab. Logging out of an
Outlook Web Access server clears cookies for all tabs in the same window, ending your PRPC session. All
uncommitted work is lost; log in again to start a new session.

Cookies
PRPC requires persistent cookies. Ensure your browser settings allow cookies. For browsers that allow
exceptions, an alternative is to disable cookies but add the nodes hosting your PRPC application to the list
of "allowed" sites.

ActiveX controls not supported


ActiveX controls are only supported in Internet Explorer. Safari, Chrome and Firefox users are unable to use
functions that rely on ActiveX controls. See Understanding ActiveX for more information on how these
controls are used by PRPC.
The Designer Studio and cross browser compatible applications built on PRPC are accessible using Microsoft
Internet Explorer 8, 9, and 10.

Restrictions on file downloads


If your PRPC server is identified by an IP address or by a domain-qualified name (such
asmyserver.mydomain.sub) in the browser's address line, you may be prompted before downloading a file.
This can restrict your ability to use file attachments. To avoid this restriction, ensure your browser has the
"Always prompt before downloading" option disabled.

Scripting
PRPC uses JavaScript. Applications may use VBScript in addition to JavaScript. Ensure your browser has
JavaScript enabled.

Cache Settings
Temporary Internet Files
The open authoring facilities (including those for text files, HTML, XML, Excel, and Word) save temporary
files on the user's workstation, or on a local directory that is 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, make sure that these variables 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.
Page refresh settings
PRPC uses HTTP 1.1 and marks pages as expired when appropriate. No exposed method is available that
allows a user to instruct the browser to automatically clear the browser cache when the user refreshes a
page. You can, however, manually clear the cache by reviewing your browser's "history", "browsing data" or
"network" settings.
The system responds best if your browser cache is enabled, because the cache can store images and other
static files locally. Browser caching is not required.

Performance tips
Developers and users are most productive if they remember these tips:

Click the Pega logo in the header of the Designer Studio to open the Home Page

Use keyboard shortcuts in conjunction with default browser hot keys

Use the Actions > Refresh action found on all form headers to refresh only the form in focus

16

Review browser add-ons for any unnecessary entries. Certain non-Microsoft add-ons can
significantly impact performance of the Designer Studio

Do not use the browser refresh hot key F5 when using multiple tabs in a single session

Do not use the browser history capabilities, Back icon or keyboard shortcut to return to an earlier
page; stale information can interfere with PRPC server synchronization

Browser
Developers and application users access instances of PRPC through a web browser. The following browsers
are supported by the Designer Studio:

Internet Explorer

Mozilla Firefox

Google Chrome

Apple Safari

Applications built on PegaRULES may not operate correctly in all supported browsers if they requireActiveX
controls or include custom (non auto-generated) user interface rules. As a best practice, upgrade your
existing applications to use the HTML5 Document Type.

Understanding ActiveX controls


As you use PRPC, Internet Explorer automatically prompts you to download Microsoft ActiveX controls(also
known as OCX files) to support special functions.
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. Once downloaded,
ActiveX controls reside in the Downloaded Program Files directory. See PDN article How to download all
ActiveX controls at once.

Browser settings
Review your Internet Explorer security settings on the Tools > Internet Options > Security panel.
Depending on which settings you have selected, 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 these
dependencies, right-click the file name and choose
Properties from the menu, and then click
theDependency tab.
NOTE: 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.

Shipped ActiveX controls


The following features require ActiveX controls. You are prompted to download an ActiveX control when you
attempt to use the associated feature. For example, the prompt to downloadprOpenAuthoring appears
when you try to edit a Java step in an activity externally.
ActiveX controls are specific to supported browser versions of Internet Explorer. When usingsupported
browsers other than Internet Explorer, you may find that these features are disabled or display a warning.

17

Feature

Details

ActiveX dependencies

Form Builder

Supports Form rules.

FormBuilder.ocx

Image Viewer

Scanning, manipulating, and viewing


scanned attachments.

PegaImgViewer.ocx

pegaimageviewer.inf
comct332.ocx
comdlg32.ocx
lfbmp12n.dll
lfcmp12n.dll
lfpng12n.dll
ltdlg12n.ocx
ltkrn12n.dll
ltocx12n.ocx
lttwn12n.dll
mscomctl.ocx
msvbvm60.dll
olepro32.dll
asycfilt.dll
comcat.dll
lffax12n.dll
lfgif12n.dll
lftif12n.dll
ltdis12n.dll
ltdlg12n.dll
ltefx12n.dll
ltfil12n.dll
ltimg12n.dll
objsafe.tlb
oleaut32.dll
stdole2.tlb
msinet.ocx
Performance Analyzer
tool

Captures trace details from the client.

PegaClientSupport.ocx

pegaclientsupport.inf
objsafe.tlb
Outlook calendar
integration

PegaOutlookAddInCaller.ocx
Used by the Get Appointment
List orSend Meeting Request flow action

18

to communicate with an operator's


Microsoft Outlook calendar.

PegaOutlookAddIn.dll

See PDN article Integrating with Outlook PegaOutlookAddInCaller.dll


calendars.
Dynamic menus

The Menu Bar control and menus used in


prDynamicMenus.ocx
some portal rules.
prdynamicmenus.inf
MSXML.dll Microsoft

Data Table editor

Using the Edit In Excel option in list


views and data tables.

prImportManager.ocx

prexcelmanagertemplate.xls
prexcelgenerictemplate.xls
primportmanager.inf
Open Authoring

Supports dispatching of Microsoft Word,


HTML, Java, and XML editors and
conversion of Word files to PDF form
using the Amyuni Technologies print
driver.

prOpenAuthoring.ocx

blankinfozipfile.zip
blankdocument.tif
openauthoring.inf
acfpdfu.dll Amyuni
Technologies
acfpdfui.dll Amyuni
Technologies
install.exe Amyuni
Technologies
acfpdf.txt Amyuni
Technologies
cdintf.dll Amyuni
Technologies
vbuzip10.dll Info-ZIP
vbzip10.dll Info-ZIP

Com Interface

Screen shot
attachments

Developing Microsoft Component Object


Model (COM) objects using Visual Basic prPackageComInt
and Service COM rules.
prScreenCapture.ocx

pegajpeglibrary15.dll
legintwincapture.inf
msvbvm60.dll Microsoft
ascyfilt.dll Microsoft

19

Application Document
Wizard

Supports embedding Entity Relationship prVisioInterface.ocx


Diagrams in generated Word
documents.
propendownload.exe
visinvisiosupport.dll
prvisiointerface.inf
idle_visio_doc.vsd
visindoclaunch.dll
keyhook.ocx

Avoiding ActiveX controls


There may be cases where a system does not allow downloads of ActiveX controls from vendors other than
Microsoft. To ensure your application does not rely on any Pegasystems Inc. ActiveX controls, you can:
1

Copy the 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 the access groups for workers and managers, reference the new portal rules.

In your application design and implementation, exclude capabilities that require any of the ActiveX
controls listed 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 report definition, turning off this option.

Notes

Local Zone security settings must be enabled to allow successful ActiveX control downloads.
See How to set up Internet Explorer for more details.

ActiveX controls are stored as Binary File rules with CAB (cabinet) as the file type.

Developers can access a PRPC application as a service through an ActiveX control that they create
as part of a Service COM interface.

When a user accesses different versions of PRPC from one workstation, conflicts can occur 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
all CONFLICT directories. (In some cases, you may need to use a Windows CMD session to see and
delete the CONFLICT directories.)

Before 2001, Microsoft ActiveX controls were called OLE controls.

In many cases, ActiveX controls require storing temporary files on your local machine.

20