Access Group form
Completing the Settings tab

Field

Description

Identify a portal rule to indicate which portal presentation supports those requestors who reference this access group. Click the pencil icon () to open the portal rule.

Select a portal layout that works with the Roles array on the Layout tab. Typical choices referencing standard portal rules are:

• For a worker, select the Case Worker composite portal pyCaseWorker.
• For a manager, select the Case Manager composite portal pyCaseManager.
• For a business analyst, select BusinessAnalyst.
• For all developers and system administrators, select Developer.

The BusinessAnalyst portal is designed to support business analysts who have the PegaRULES:SysArch4 access role. Do not choose BusinessAnalyst unless PegaRULES:SysArch4 appears in the Roles array on the Layout tab and Allow rule check out? is selected on the Advanced tab in the Operator ID form.

The Developer portal is designed to support application developers who have the PegaRULES:SysAdm4 access role. Do not choose Developer unless PegaRULES:SysAdm4 appears in the Roles array on the Layout tab and Allow rule check out? is selected on the Advanced tab in the Operator ID form.

Select to cause users associated with this access group to see more-accessible versions of several standard harness, section, and flow actions rather than the normal standard versions. To provide maximum accessibility support, also include the PegaWAI RuleSet in the RuleSet list for such users. See Understanding accessibility.

Enter a number of seconds after which the system challenges idle browser sessions (for users of this access group), asking users to re-enter their Operator ID and password. This timeout event does not cause session context or clipboard contents to be lost.

If users respond to the challenge and are re-authenticated, they can usually continue processing where they left off, unless the system released locks they held in the meantime, or the system was stopped and restarted.

This authentication timeout is not related to the timeout/browser value in the prconfig.xml file or Dynamic System Settings, which controls when passivation occurs. See timeouts.

Typically, accept the default of /webwb. Directories within this directory hold important static XML forms, JavaScripts, style sheets, and images.

If you have changed the name of this directory, enter the new directory name here.

Optional. For developers and business analysts, you can define alternative layouts, to allow them to quickly switch between layouts; this is useful in debugging. Enter the name of a user-role-based portal rule to make an additional portal presentation available to a developer or business analyst.

For example, if your Default Portal Layout is Developer, you can add one of the user-role-based portals such as pyCaseManager, pyCaseWorker, User, or Manager here. Then in the Designer Studio, you can switch to the pyCaseWorker portal to run a process and see it as the end users would see it.

As a best practice, if the Default Portal Layout field identifies a traditional ('fixed') portal, leave this array blank or list only other traditional portals here. Similarly, if the Default Portal Layout field identifies a composite portal, leave this array blank or list only other composite portals here. Do not mix the two kinds of portals.

Portal switching at runtime

From the Designer Studio or Business Analyst portal, users can switch rapidly among portal layouts by choosing > Open Portal > portalname. (However, you cannot switch between the Designer Studio and the Business Analyst portal using Open Portal.)

From the WorkManager portal, users can switch using the Portal Layout drop-down list.

Leave these fields blank for an access group that supports logging on to PRPC from external systems, or that supports workers or managers who never create rules.

Optional. Select a RuleSet from those listed in the Production RuleSets array on the Layout tab, or from those listed in application rules referenced on that tab, that the system suggests as a destination RuleSet when users associated with this access groups create a rule.

• If this access group is to support application developers — users who can create rules — select a RuleSet that the developers usually work in and add rules to.
• For managers who are to customize reports, select a RuleSet that is not intended to be moved to other PRPC systems.
• For language specialists involved in internationalization, select a language-specific RuleSet.

When a user associated with this access group uses the New button () or Save As button () to create a rule, the system suggests this RuleSet for the new rule.

If you leave this field blank, the Save As form uses the RuleSet of the existing rule being saved as the default RuleSet for the new rule, if a version that is unlocked is available to you.

Optional; required if RuleSet is not blank. Enter the RuleSet version (for the RuleSet identified in the previous field) that requestor associated with this access group usually add rules into. During New operations (and certain Save As operations). this version appears as the default RuleSet version.

Select to disable the Application-Based Assembly (ABA) mode for requestors that use this access group. When selected (and certain other conditions are met), PRPC uses the pre-V6.3) rules assembly cache mode for requestors that use this access group. The rules assembly mode generally provides inferior runtime performance.

As a best practice for applications developed in V6.3+, do not select this checkbox. As a best practice for applications developed in versions before V6.3, do not select this checkbox unless your application uses branch RuleSets, mobile RuleSets, shared RuleSets or component RuleSets. If your application uses these specialty RuleSets, testing of ABA mode is recommended to assess functional equivalence of the two modes. See Understanding Application-Based Assembly mode.