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 Access tab. Typical choices referencing standard portal rules are:

• For a worker, select the traditional portal WorkUser or composite portal User.
• For a manager, select the traditional portal WorkManager, or composite portal Manager.
• For all developers, select Developer.

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 Access tab and Allow rule check out? is selected on the Security tab.

To retain support for access groups introduced in Version 4, the additional portal rule SysAdminDD remains available. This portal rule is deprecated and not recommended for use in new access groups.

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.

Typically, set the authentication timeout value in this field to a period that is much shorter than the requestor timeout set in the timeout/browser value in the prconfig.xml file. See timeouts.

Through a prconfig.xml setting, you can disable the authentication challenge that normally appears after this time-out occurs:

<env name="Initialization/noAuthenticateOnActivate" value="true" />

The default setting is false.

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, you can define alternative layouts, to allow them to quickly switch between layouts; this is useful in debugging. Enter the name of a portal rule to make an additional portal presentation available to this user.

As a best practice, if the Default Portal Layout field identifies a traditional 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 WorkManager portal, users can switch using the Portal Layout drop-down list.

From the Developer portal, developers can switch rapidly among portal layouts by choosing File > Open > Portal > Portalname.

Leave these fields blank for an access group that supports logging on to Process Commander 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 Access 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 Process Commander 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.