Table of Contents

Agents rules

An agents rule provides configuration information for the agents listed in the rule, including the trigger or wake-up interval or schedule, the activities that the agents execute, and the way that the agent queue is handled. Each agent in the list performs one request (for example, sending generated correspondence or processing assignments) by running the associated agent activity.

The name of an agents rule is the name of a ruleset, and there can be only one agents rule defined for each ruleset and version in a Pega Platform system. When the Agent Manager master agent notices a newly added agents rule, it generates agent schedule data instances for each node in your Pega Platform application.


Use the Records Explorer to list all the agents rules that are available to you by selecting SysAdmin Agents . The list includes the standard agents rules. You cannot add background processing activities to the standard agents; instead, create new agents rules that run your agent activities.


Agents rules are instances of the Rule-Agent-Queue class. They are part of the SysAdmin category.

Changes to agents rules

An agents rule provides a template that specifies the global settings for that agent on all nodes. To modify the configuration settings for an agent, open the generated agent schedule object for a specific node and modify the settings in the agent schedule.

After you save a modified agents rule, delete the agent schedule instances so that the Agent Manager generates a schedule with the updated rule information.

Agents are not authenticated requestors

Agents are not full authenticated requestors. As a result:

  • Agents do not have an associated organization, division, or unit.
  • Agents cannot execute activities that have the Authenticate? check box (on the Security tab of the Activity form), unless the Bypass activity authentication check box (on the Security tab of the Agents form) is selected.
  • Agents do not have an associated business calendar. The batch requestor honors the default server locale settings, including the default calendar when executing agent activities that contain business calendar logic.
  • Agents operate using the clock time of the server on which they run.
  • Although the agents rule form contains a version, the Agent Manager does not use rule resolution to determine which version of an agents rule to run. The highest version always runs.
  • Creating a Job Scheduler rule

    To perform tasks and jobs that are configured to run on a periodic basis, such as bulk processing or system cleanup jobs, create a Job Scheduler rule.

  • 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:

  • Completing the Schedule tab
  • Completing the Nodes tab

    The Nodes tab displays a read-only list of the agent schedule instances generated for this agents rule. Click a row to open an agent schedule.

  • Pega-AutoTest agents

    The agents in the Pega-AutoTest ruleset perform processing of unit test suites.

  • Pega-DecisionEngine agents

    The Pega-DecisionEngine agents support Decision Management operations.

  • Pega-EndUserUI agent

    The agent in the Pega-EndUserUI ruleset performs periodic purging of orphan tags from the database table pr_data_tag.

  • Pega-ImportExport agent

    The agent in the Pega-ImportExport ruleset supports certain one-time post-upgrade processing.

  • Pega-IntSvcs agents

    The following agents in the Pega-IntSvcs ruleset process queued service and connector requests .

  • Pega-ProcessEngine agent

    The Pega-ProcessEngine agent performs three types of background processing:

  • Pega-ProCom agents

    The agents in the Pega-ProCom ruleset process email, service-level agreements, and assignments. The agents in this rule provide the following types of processing:

  • Pega-RuleRefactoring agent

    The agent in the Pega-RuleRefactoring ruleset supports the Ruleset Maintenance wizard by periodically searching for queued refactoring tasks and executing those it finds. These tasks include copying, moving, merging and renaming rulesets and ruleset versions.

  • Pega-RULES agents

    The four agents in the Pega-RULES ruleset perform general system housecleaning and periodic processing:

  • Pega-RulesEngine agents

    The agents support periodic maintenance of the system cache, event processing, the Property Optimization tool, and report statistics. In a multinode cluster, you can enable these agents on multiple nodes.

Related Content



Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.