Back Forward Agent Schedule instance
Completing the Security tab

 About Agent Schedule data instances

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:

If there isn't an access group specified on this tab or on the Security tab of the agents rule, Process Commander 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 rules, performing escalation when the deadlines and goals in service rules are not met. If your application uses service level rules, ensure that the access group referenced in the Pega-ProCom agent schedules includes your application RuleSets and versions. You can update the PegaRULES:Agents access group, or maintain another access group that includes the RuleSet versions that cover all applications in your system that use service level rules.

Field

Description
Access Group

SmartPromptOptional. Select an access group to use by the legacy and advanced agents listed in this agent schedule.
Bypass activity authentication

Optional. Agents run as internal background processes and are not authenticated the way interactive users and other requestors are. If the agent's processing calls an activity that has the Requires Authentication option selected on its Security tab, Process Commander reports an error in the Pega log.

Select this option to allow this agent to run activities that require authentication, even if the agent is not authenticated. (See PDNPega Developer Network article PRKB-25055 Agents throws exception when running authenticated activities.)

zzz About Agent Schedule instances