The name of an agents rule is the name of a RuleSet and there can be only one ag

ents rule defined for each RuleSet and version in a Process Commander system.
PDN article PRKB-25049 How to modify an agent.
QUEUE MODES OF AGENTS :
Legacy
Specifies that this is an agent that was created in a version prior to V5
.4 and has not yet been updated. This option is not available for agents created
in V5.4 or later.
Standard Specifies that this agent processes items from an agent queue and that
it relies on the system to provide object locking and other transactional suppor
t. AQM IS NOT ENABLED BY DEFAULT.
Advanced Specifies that this agent uses custom queuing.
See PDN article PRKB-25044 How agent queues work.
MAX RECORDS AND AUTO QUEUE MANAGEMNT ARE FOR STANDARD AGENTS.
Agents with the Standard queue mode do not need access groups. For standard agen
ts, 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 ite
m.
PDN article PRKB-25055 Agent process throws exception when running authenticated
activities.
The standard agents rules:
Pega-AutoTest : The agents in the Pega-AutoTest RuleSet perform processing of un
it test suites.
Pega-EndUserUI : The agent in the Pega-EndUserUI RuleSet performs periodic purgi
ng of orphan tags from the database table pr_data_tag.
Pega-EventProcessing : The aGent in the Pega-EventProcessing RuleSet, when enabl
ed, supports processing of business events identified in Event Definition rules.
Pega-ImportExport : The agent in the Pega-ImportExport RuleSet supports certain
one-time post-upgrade processing.
Pega-IntSvcs : Five agents in the Pega-IntSvcs RuleSet process queued service an
d connector requests and perform maintenance for PegaDISTRIBUTION MANAGER
Pega-ProcessEngine : agent performs three types of background processing:
Case type calculations
Incoming email processing
Flow dependency processing
Pega-ProCom : The agents in the Pega-ProCom RuleSet process email, process servi
ce level rules and assignments, and so on. The agents in this rule provide the f
ollowing types of processing:
Processing service level events and escalation (ServiceLevelEvents)
Applying a flow action to assignments in bulk (AgentBulkProcessing)
Sending out email correspondence (SendCorr)
Retrieving PDF files from the PegaDISTRIBUTION Manager (GetConvertedPDFsFromPDM)
Checks whether starting flows references have been updated (GenerateStartingFlow
s)
Checking incoming email (deprecated in V5.3) (Email_CheckIncoming)

Pega-RuleRefactoring
Pega-RULES The agents in the Pega-RULES RuleSet perform general system houseclea
ning and periodic processing. This agents rule has six agents:
SystemCleaner
SystemPulse :
The Pega-RULES agent performs periodic processing known as a system pulse. This
processing synchronizes the contents of the in-memory rule cache on that node wi
th rules stored in the PegaRULES database. The pulse helps each node coordinate
processing and synchronize operations, including the contents of the rule cache.
SystemIndexer
RuleUsageSnapshot
StaticContentCleaner
SystemWorkIndexer
Pega-RulesEngine
The Agent Manager is a master agent that gathers and caches the agent configurat
ion information set for your system when Process Commander starts. Then, at a re
gularly scheduled interval, it determines whether any new agents rules were crea
ted during the last period.

A commit
pt those
box). If
s a lock
sion may
erform a

operation causes locks held by a requestor session to be released (exce

for objects opened without selecting the Obj-Open ReleaseOnCommit check
after a commit operation by one requestor
a different requestor acquire
on an instance needed by the current requestor session, the current ses
be unable to progress. To eliminate this possibility, flow executions p
commit operation only at specific times:

Queue-for-Agent : Use this method when constructing the application

logic that queues items such as work objects or
assignments to be processed in the background by
an agent.

Agents :
1. Internal back ground process,tasks on periodic basis
2. Tasks are according to the defined rules(sending email notification), system
tasks(synchronizing caches on multi node-Pulse).
3. Agent are
(1) Task driven are picked from a Queue. Queue items are created during work i
tem processing.
Ex: SystemCleaner : System cleans all the temporary db objects every mornin
g. For this a Queue entry is needed.
(2) schedule Driven dont use queue entries rater directly run a activity to pe
rform a task
4. Agent Modes :
(1)Legacy: prior to 5.4 for backward compatibility. there is no queue function
ality they just wake up and run.
(2)Standard: Transactional processing is handled by PRPC, leverages the agent
queue functionality, only contains business logic.

(3)Advanced :Transactional and Business processing. Queue Functionality explic

ity: call the queue agent or processing without any queue.
Agent Queue : It is defined by the class and entries are instances of that class
.
Default class is System-Queue-DefaultEntry. If we want to create a new class it
should be extended from System-Queue-. Entries are added by Queue-For-Agent acti
vity method or QueueForAgent Activity. They should be committed to db before cal
ling the Queue-For-Agent activity method or QueueForAgent Activity.
AQM(Auto Queue management)
1. It can be enabled or disabled on any agent.
2. Scheduled --> now-processing --> Broken-Process or Success. It manages the pr
ocess and maintains the status by locking at each stage.
3. If Enabled entry is locked in processing stage. It release when commit or rol
lback occurs. If the processing is failed then it is kept in Queue in Broken-Pro
cess. Someone can fix the issue then requeue the entry again.
4. If Disabled then AQM gets only one chance to process the entry there is no pl
ace to save the failed entry.
Agents are Instance of Rule-Agent.
One Agent rule per RuleSet.
Perodic is run and slept for Interval time specified.
Recurring on evry day configured.
Agnet Schedule are created by System. If the Agent is in locked ruleset chnages
can be done in Agent Schedule.
Standard Agents dont need access group as the Queue is populated with respective
Access Group data so this is not needed.
Standard Agent Processing :
For Each Agent marked enabled,Agent manager wakes up the Agent Thread and create
a brand new requestor
Check the Agent queue for Entries in System-Data-DefaultEntry(pr_sys_queues).
If nothing found goes back to sleep for specified interval.
If one or more are found. then system lock the first entry and open and process
that.
If all the processing is sucees then commit is happned or rollback happens.
if AQM is enabled then failed data is kept in Queue, if disabled removed from qu
eue.
Tracing A agent
1. Delay the agent in Agent Management --> Agents
2. Click on Requestor Management and refresh it until a new requestor with messa
ge with waiting
3. Select it and tracer button.