Requestor Type form
Completing the Initial tab

Field

Description

Select an Application-based Access Group.

The choice Lists of RuleSets and Roles remains available for Requestor Type data instances created in Version 4 systems. However, this approach is deprecated for new development.

Optional. Identify an access group that contains an application rule and one or more access roles. The RuleSets and versions identified in the application rule in this access group become visible (to rule resolution) for all requestors of this type.

Except as described below, enter only one row in this array, and select the radio button for that row.

For the BATCH instance, you can list additional access groups that are to be available to legacy agents, for the agents where the Agents field on the Security tab of the Agent Queue data instance is blank. For example, list access groups for the Pega-ProCom agent here; the agent needs application-specific access to send correspondence and to find and enforce service level rules (SLAs). (If the Agents field on the Security tab of the Agent Queue data instance is not blank that access group is used, and the list in the BATCH requestor data instance is ignored.)

For the BROWSER instance, you can list additional access groups that are to be available to all browser users — includingunauthenticated users — through the application switching facility. However, as a best practice, list such access groups in an Organization data instance, rather than in the BROWSER requestor data instance, to restrict access to authenticated users.

You may enter additional access groups in this array for requestor data instances other than the BATCH and BROWSER instance. However standard rules ignore all rows except the single access group that is marked with a selected radio button. This array is not a means to provide more than one access group to services or portlets.

Field

Description

RuleSet or RuleSet:Version. Order is significant.

Access role. Order is not significant.