Agents rule
form
|
Use the Security tab to specify the access group to be used for the following kinds of agents:
Legacy
Advanced
but they
do not use the agent queue functionalityIf you do not specify an access group for legacy and
advanced agents that do not use the agent queue function,
Process Commander uses the access group specified in the
Batch
requestor type (that is, the
Data-Admin-Requestor instance named
Batch
). Agents whose mode is Standard
do not need access groups; for standard agents, each queue item
is processed in the authorization context of the user whose
actions or processing (work object, assignment, and so on)
generated the queued task.
Field |
Description |
Access Group |
Optional. Select the access group to use for
the legacy and advanced agents listed in this rule. This
field is ignored for agents with a type of
|
Bypass activity authentication |
Optional. Agents run as internal background processes and are authenticated differently than operators. If the agent's processing calls an activity that has the Requires Authentication option selected on its Security tab, Process Commander throws an error. Select this option to allow this agent to run activities that require authentication, even if the agent is not authenticated. (See Pega Developer Network article PRKB-25055 Agent process throws exception when running authenticated activities.) |
See also Pega Developer Network article PRKB-25047 How to configure access groups for agents.