Agent schedule data instances – Completing the Security tab

Use the Security tab to override the access group the following kinds of agents specified in the corresponding agents rule from which this agent schedule instance was generated:

  • Agents whose queue mode is Legacy (agents created before PRPC Version 5.4)
  • Agents whose queue mode is Advanced but do not use the Queue Manager or queues
Note: 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 queued task.

If there isn't an access group specified on this tab or on the Security tab of the agents rule, the Pega Platform uses the one specified in the Batch requestor type (that is, the Data-Admin-Requestor instance named Batch ) for legacy and advanced agents that don't use queues. Agents whose queue mode is Standard do not need access groups; for such agents, each queue item is processed in the authorization context of the user whose processing or actions generated the queued task.

Note: One of the Pega-ProCom agents enforces service-level agreements, performing escalation when the deadlines and goals are not met. If your application uses service-level agreements, ensure that the access group referenced in the Pega-ProCom agent schedules includes your application rulesets and versions. You can update the <organization>:Agents access group, or maintain another access group that includes the ruleset versions that cover all applications in your system that use service-level agreements.
Field Description
Access group Optional. Specify an access group to use by the legacy and advanced agents listed in this agent schedule.
Bypass activity authentication Optional. Select this check box to allow this agent to run activities that require authentication, even if the agent is not authenticated.