More about Requestor Type data instances

Requestors may be unauthenticated, known as guest users, or authenticated.

The access groups and activities specified in requestor type instances are the minimum necessary to provide access as a guest. To acquire more capabilities, a requestor can become authenticated, usually by supplying an ID and password that matches those in an Operator ID instance.

Requestor types and the system name

The system name (from a Data-Admin-System instance) is a key part of each requestor type instance. You can choose a system name during installation, and you can change it later. A landing page tab assists in changing the system name. Select Designer Studio > System > Setting > System Name. See System category — Setting landing page.

Spawning multiple background requestors

A BATCH requestor — for example an agent or service — can achieve a degree of parallel processing by starting a second requestor through a Java step similar to the following PublicAPI call:
tools.getRequestor().queueBatchActivity("<Applies To class>", " <activity-name>", tools.getParameterPage());

The requestor can send parameters to the called activity on the current activity's parameter page. The second requestor session has the same access group as the current requestor session. It executes the activity and terminates.

The combined throughput of both requestors depends on available JVM memory, processor, and other demands on the system.

Use care to avoid locking, contention, and deadlocks when using this facility,

Capabilities provided by the BROWSER requestor type

Guest users — unauthenticated requestors — typically have access to rules in the RuleSets provided in the PRPC:Unauthenticated access group, as referenced in the Requestor type instance named pega.BROWSER.
If you update the BROWSER requestor type to reference a different access group, or update the PRPC:Unauthenticated access group to make additional RuleSets available to unauthenticated users, review carefully the Authenticate? check box on the Security tab of each activity in the RuleSets. Select this check box for all but those specific activities that guests need to run.