Developer portal basics — Setting preferences

Label

Description

Select to cause the portal to open at full screen size the next time you log in.

Clearing this check box when in full screen mode has no immediate effect. To reduce the portal window for the current session, use Windows operations.

The In field affects the portal behavior when you enter a new work object from the Developer portal through the Run > Process menu selection.

Select to control where work object forms appear:

• View — Presents the work object entry form, assignments, and other user interactions in the Developer portal workspace.
• Pop-Up — Presents the work object entry form, assignments, and other user interactions in a pop-up window, closed after each submission.
• New Portal — Presents the work object entry form, assignments, and other user interactions in a separate window and separate Thread.

If you chose New Portal for the In field, select a portal rule to be used.

Optional. Select a skin rule to use in the Run Process In portal. If not blank, this skin rule overrides the skin rule identified in the portal rule, when you open, edit or preview a harness, section, or flow action rule, or execute a flow using Run > Process > zzzzzz.

Select to require a confirmation each time you click the Log off link.

Select to require a confirmation when you use the Close button () for a rule or data form that contains modified but unsaved data.

Select to disable default processing that strips out white space and comments from JavaScript files before they are sent to a browser. When enabled, this feature improves performance by reducing the size of JS files, reducing traffic and the browser memory required to hold the script. As a security measure, this feature also scrambles (obfuscates) variable names.

Leave disabled unless you are debugging JavaScript files and you need to read the JavaScript code (in the HTML source code of the browser window)

Label

Description

Select to allow use of keyboard shortcuts in the Developer portal, such as CTRL + 0 to log off. Clear to disable these shortcuts.

Click to reset all keyboard shortcuts to the default values.

Click to display all of your current keyboard settings.

To view or change a single keyboard shortcut, select a Category from the list in the left panel and then select a Command from the list in the right panel.

Define a shortcut for the selected command, by selecting or clearing check boxes for the CTRL key, the ALT key, and a letter, digit or function key. Select at least one of the CTRL or ALT check boxes.

Chose shortcut assignments carefully. This facility allows you to override (reassign) keyboard shortcut values that are defined by Microsoft Internet Explorer, such as CTRL+ C for Windows clipboard copy or CTRL + V for Windows clipboard paste, while using the Developer portal. Consult Microsoft Help for a complete list of built-in shortcuts.

Click Save to record your changes.

Label

Description

Label

Description

Set these preferences to affect the appearance of open forms in the Developer portal.

Select to present a newly opened rule or data form with the header visible () rather than collapsed (). See Identifying parts of rule and data forms.

Select to cause the Developer portal to show a tab for each open rule form or data form. Click a tab to bring the rule to the front.

The tab label generally identifies the final key part or part (corresponding to the pyRuleName or pxInsName property). For rules or data instances that have a multipart key, the earlier key parts — for example, the Applies To key part of a property rule — does not appear.

Changes to this check box take effect the next time you log in.

Select to control how many rules (or data instances) can be open at once and shown in the Currently Open Views list (). The default is 20, the maximum allowed. When you reach this maximum, you can't open an additional form until you close another. See Developer portal — Working with the Views display.

Changes to this value take effect the next time you log in.

Set two preferences to affect the operation of the portal after you click the Delete toolbar button ().

Select to ask for confirmation for each requested Delete () operation.

Select to close a rule form or data form immediately when a Delete operation is successful.

Set the Auto Check-out preference to control check-out.

Select to automatically check out a new rule you create with the Save As () toolbar operation. (Checkout occurs only when both the RuleSet containing the new rule and your own Operator ID are enabled for checkout.)

Set these preferences to affect the operation of the Flow form.

Select to automatically hide the navigation panel when editing a flow in Visio. This allows more of the form to be visible at once.

Select one of three Visio templates to use when creating new flow rules:

• Standard — Icons and shapes implemented in Version 5.3, such as for an assignment task. These shapes are functionally equivalent to Classic shapes.
• BPMN — Shapes used in Business Process Modeling Notation, such as for an assignment task.
• Classic — Shapes used in Version 4, 5.1, and 5.2, such as for a Decision task.

Existing flow rules are not affected by this preference, even when you later update them.

You can override this preference when you create a single flow rule by completing the Use Template field on the New form. See Flow rules — Completing the New Form.

When editing a flow rule in Visio, you can change the current stencil using the Flow Properties panel. See Flow rules — Editing in Visio — Flow properties.

Select Portrait or Landscape to control the default presentation of flows in Visio. You can override this setting for a flow rule in the Flow Properties panel. See Flow rules — Editing in Visio — Completing the Flow Properties panel.

Select the stencil that is the default for new flow rules you create. You can select another stencil when completing the New form for flows, or change the stencil in the Flow Properties panel. See Flow rules — Editing in Visio — Completing the Flow Properties panel.

Select to apply changes you make to a Cell Property panel, Layout panel, or other similar panels automatically as soon as you tab from a field.

When this option is selected, the panel is pinned.

Select:

• Warn Always — A warning of potential loss of your inputs occurs if you click OK without previously clicking Apply (or Cancel). You can cancel the close.
• Warn when not pinned — A warning occurs if the Cell Properties panel is not pinned to a fixed location and you click OK without previously clicking Apply (or Cancel).
• Never warn — No warnings occur. Changes you made (if any) since last clicking Apply are lost.

(If selected, a warning dialog appears if you close a panel without clicking Apply or Cancel.)

You can't change this setting when Auto-Apply is selected.

Label

Description

Select to cause the Developer portal to display all four Explorers. Clear to select Explorers individually. Excluding Explorer tools you never use can improve the performance of the Developer portal.

Select to display the Application Explorer in the navigation panel. See About the Application Explorer.

Select to display the Used by App Explorer in the navigation panel.

Select to display the Class Explorer in the navigation panel. See About the Class Explorer.

Select to cause the navigation panel to include the Rules by Type Explorer. See About the Rules by Type Explorer.

Click to review or modify Application Explorer preferences. See Setting Application Explorer preferences.

Click to select which base classes and other top-level classes appear in the Class Explorer selection box. See Setting Class Explorer preferences.

Check to cause a small alert window to appear when your requestor session produces an alert. (The window does not interfere with processing or typing and disappears quickly; no click is required to dismiss it.) See Working with the My Alerts tool.

These controls affect the order and labeling of nodes in the Class Explorer and Application Explorer trees. These settings do not affect which rules and classes appear.

Select:

• Parent — Presents subclasses to the right of the class identified in the Parent (directed inheritance) field on the Basic tab
• Pattern — Presents subclasses to the right of the class based on pattern inheritance.

For example:

• Under Parent inheritance, the class PegaSample-SimpleTask (a work type) appears as a subclass of Work-Object-. Under Pattern inheritance, the PegaSample-SimpleTask class appears as a subclass of PegaSample.
• Under Parent inheritance, the Rule-Obj-FlowAction class appears as a subclass of the Rule-HTML-Section class. Under Pattern inheritance, the Rule-Obj-FlowAction class appears as a subclass of the abstract Rule-Obj- class.

Select how objects are identified in the Class Explorer and Application Explorer:

• Name — Presents the name (or a segment of a class name)
• Label  — Presents the Short Description text

Select a count (10, 20, 50, or 100) that determines how many rules or data instances appear on the Views list () when you display Recently Opened rules. See Developer portal — Working with the Views display.

Label

Description

Label

Description

Select a value between 5 and 50 to limit how many initial search responses are initially displayed. A lower limit produces faster response.

Regardless of the limit you set, you can access a full set of search responses by clicking the More... link from the Find results pop-up.

Select one of four Find searches as the default search type:

• Most Recent — Displays in the Find box and makes searching for recently updated rules the default search type.
• My Most Recent — Displays in the Find box and makes searching for rules updated by you become the default search type.
• Rule Content — Displays in the Find box and makes searching for a word anywhere in a rule the default search type.
• Work — Displays in the Find box and makes opening a work object based upon a work object  ID the default search type.

You can select another search type at any time by clicking the icon corresponding to your Search Type selection.