Agents with the Standard queue mode 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 item, assignment, and so on) generated the queue item.
Agents rule form
|
|
Use the Security tab to specify the access group to be used for the following kinds of agents:
LegacyAdvanced but they do not use the agent queue functionality
Agents with the Standard queue mode 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 item, assignment, and so on) generated the queue item.
If you do not specify an access group for legacy and advanced agents that do not use the agent queue function, PRPC uses the access group specified in the Batch requestor type (that is, the Data-Admin-Requestor instance named Batch).
Field |
Description |
| Access Group |
|
| 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, PRPC throws an error. Select this option to allow this agent to run activities that require authentication, even if the agent is not authenticated. (See PDN article Agent process throws exception when running authenticated activities.) |
See also PDN article How to configure access groups for agents.
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 
About Agents rules