Table of Contents

Configuring queue processors in Pega Sales Automation

In Pega Sales Automation 8.3, all agents are changed into queue processors to give you more flexibility, stability, and scalability for background processes. Because of this change, all agents are disabled and deprecated. All queue processors are active by default, but you must include background processing for the SalesAutomation and PegaCRMBase rules. You can also further customize queue processes and configure the System Runtime Context.

The GeoCode agent configuration, which was defined in the PegaCRM ruleset, is now defined as a queue processor in the PegaCRM-SFA ruleset.

Including background processing

For the introduced queue processors to work, you must include background processing for the SalesAutomation and PegaCRMBase rules. If there is an implementation layer build on Sales Automation, you must perform the steps below for the appropriate application rule as well.

  1. Log in to Pega Sales Automation as an administrator.
  2. In the Dev Studio header, click Sales Automation > Definition.
  3. On the Definition tab, in the Application rulesets section, click Advanced and verify whether the Include in background processing check box is selected next to the SalesAutomation rule. If not, select the check box.
  4. Click Save.
  5. On the Definition tab, in the Build on applications section, verify whether the Include in background processing check box is selected next to the PegaCRMBase application rule. If not, select the check box.
  6. Optional: Ensure that the Include in background processing check box is selected for any application rules of other applications built on Sales Automation.
  7. Click Save.

Optional: Customizing queue processors

  1. Open a queue processor, for example, GenerateAccessForOperatorProcessor.
The following other queue processors are shipped with Pega Sales Automation: UpdateAccessForWorkTypeProcessor, GenerateAccessForNewTerritoryProcessor, ProcessTerritoryParentChangeProcessor, and GeoCodeInstanceProcessor.
  1. Specify the associated node, number of threads per node, and processing conditions.
  2. Click Save.

Optional: Configuring the System Runtime Context

The System Runtime Context is configured automatically, based on the application stack. However, if you want to, for example, add another application or add roles, perform the following steps:

  1. In the Dev Studio header, click Configure > System > General > System Runtime Context.
  2. Optional: To add another application, click Add application.
  3. Optional: To add roles, click Add role.
Suggest Edit

Have a question? Get answers now.

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