Back Forward How to set up Safari for application users

Safari The Designer Studio and cross browser compatible applications built on Pega 7 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...
  2. If the Safari menu bar is not visible, select the Settings icon safari settings at the top right of the screen. From the menu that displays, select Preferences...
  3. Using the keyboard, click Ctrl +,

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

Instructions

Adobe Flash Player

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 the Word merge feature.

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

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:

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.

The Designer Studio and cross browser compatible applications built on Pega 7 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 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.

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:

Definitions ActiveX, Flash Player, open authoring
Related topics Understanding ActiveX controls and PRPC

How to setup Chrome for application users

How to set up Firefox for application users

How to setup Internet Explorer for application users