Understanding the Pega-ProCom agents

The activity System-Queue-ServiceLevel.ProcessEvent supports service level processing for both assignments and work objects. Enable this row of the Agent Schedule form unless your applications use only non-BPM rules-engine facilities. 5.5

This agent uses the queuing facility introduced in V5.4 for higher throughput. Flow processing creates queue entries (instances of the System-Queue-ServiceLevel class) and the activity dequeues them and processes them. 5.5 RULE-1512 MIRATMORE?

By default, this activity starts every 30 seconds; you can choose a higher or lower interval.

You can update three standard settings rules to control how many assignments the agent processes in a batch and other parameters. See Pega Developer Network article PRKB-25249 Understanding service levels and System Settings for the Pega-ProCom agent.

The activity Assign-.AgentBulkProcessing performs background processing of flow actions in bulk against assignments, when requested through the bulk processing feature of the Process Work workspace of the WorkUser portal. See WorkManager portal — Processing assignments in bulk. PROJ-157 5.3 MARIK

Enable this row of the Agent Schedule form to allow managers to process assignments in the background.

Because this activity is designed to detect and work around locked work objects, enable this row on only one node (of a multinode cluster) unless this causes your system to have unwanted long delays in background bulk processing. Increasing the number of simultaneously executing copies of this activity may not increase throughput in proportion, because of contention for locks.

The activity Data-Corr-.Send supports outgoing email if your system contains one or more Email Account data instances with a second key part of Notify. B-25134 SR-702

This agent uses the queuing facility introduced in V5.4, allowing the agent to run on multiple nodes without risk of locking or deadlock issues, for higher throughput. GRP-403 PROJ-1380 RULE-1509

See the Pega Developer Network articles PRKB-25086 How outbound email works and PRKB-25089 How to set up outbound email.

The activity @baseclass.GetConvertedPDFsfromPDM requests that the PegaDISTRIBUTION Manager send a converted Portable Document Format (PDF) file to the Process Commander server. The agent then attaches the document as a file attachment to the original work object, using an attachment category identified in the earlier parameter to the standard activity Work-.ConvertAttachmentToPDF.C-2438

Enable the row containing this activity if your application uses the PegaDISTRIBUTION Manager (PDM) and COS to convert Word DOC attachments to PDF format.

The activity System-Queue-StartingFlows.GenerateStartingFlows supports the Integrated Work Manager by monitoring whether changes to starting flows have occured, in an application that is part of an IWM configuration.

This activity ensures that IWM gets the required changes. See Integrated Work Manager. kowal per email from marik

This agent is deprecated for V5.3 and later but remains available for backwards compatibility.

In versions before V5.3, the Incoming Mail tab of email account instances was used to configure email accounts that managed incoming email and this activity, @baseclass.Email_CheckIncoming, processed incoming email messages.

As a best practice, configure and use emailservices (rather than the email account approach) to manage incoming email. If you implement the email services approach, do not enable this agent.