Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Portal rules - Completing the Options tab

Updated on September 10, 2021

 This presentation is part of the Portals Overview Self-Study Course.

Transcript

The Options tab includes several miscellaneous portal functions and configuration choices.

Logo – Located under the Heading section, the Logo field allows developers to replace the Pega logo with a logo specific to the client’s requirements.  You must upload the binary file to PRPC and make sure the first key part of the file name is webwb.

Tooltip – The Tooltip field defines the text that is displayed should the mouse hover over the logo.

Help URL – The Help URL field will normally contain the URL for PRPC Help.  Quite often, clients will also develop their own on-line help application.  If so, the URL for that application should be entered here.  This field is optional, so if users should not have access to PRPC Help, this field can be left blank.

Show Launch / Show Logoff – Checking these two boxes causes these links to be displayed in the upper right of the Portal next to the Help link.  Clicking the "Launch" link causes a new browser session to be opened and will start a new thread in the same user session.  Clicking the "Logoff" link will call a JavaScript function that calls the Code-Security.Logoff activity which can be customized.

Show Application Selector – Allows you to control whether or not all work pools are available to users associated with this portal.  If this box is not checked, only the work pool marked ‘default" in the user’s access group will be available for use.  By checking this option you are essentially controlling access to applications. 

Monitor Activity Workspace – You must ensure this box is checked for users who are managers or developers or others who will have access to the Monitor Activity workspace.  Reports in the Monitor Activity workspace present work objects from a single selected work pool name.  Therefore users should be able to select the work pool and then the desired report.

Include HTML Fragments – The Include HTML Fragments section has two fields:  Narrow Pane and Wide Pane.  These two fields allow you to add a Rule-HTML-Fragment rule, which may provide JavaScript support or redefine styles.   You do not use these fields to add visible elements or gadgets to the Portal.

Exit Options – The Exit Options section includes two checkboxes:  Warn on Exiting and Warn When Data has Changed.   The Warn on Exiting check box causes a warning dialog box to appear whenever the user clicks the log-off link.  The Warn When Data has Changed check box causes the application to display a warning dialog box whenever the user closes a form that contains inputs not saved or submitted.

Localize – The Localize check box in the Localization section indicates that user presentation of the portal may be localized based upon field value rules in a language-specific rule set.

Download User OCX Plug-Ins – The Download User OCX Plug-Ins check box should be checked if you want to cause Windows to download certain ActiveX controls when the portal is used at runtime on a workstation that lacks the ActiveX controls, which include:

  • Data Import Manager Control
  • PegaRULES Open Authoring Control
  • PegaRULES Screen Capture Control
  • PegaRULES Visio Interface Control

The check box can be cleared if users will not be using the ActiveX controls or they have been pre-loaded on workstations.

The Developer Options includes two fields that control the options available to the user on the top bar.

  1. XML Stream:  Contains the name of a Rule-Obj-XML rule in the @baseclass class.  You may customize these by copying them into your RuleSet using a different name since the default records are marked Final.  
  2. HTML Fragment:  Can be populated with an HTML Fragment that contains JavaScript functions to support onClick() events in your customized XML rules.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us