Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Replacing an agent with a Queue Processor rule for real-time messages

Suggest edit Updated on April 5, 2022

Use Queue Processor rules for better performance and greater flexibility instead of agents. Replace an existing agent with a standard Queue Processor rule to process real-time messages.

Before you begin: Before you replace an agent with a Queue Processor rule, create the rule. For more information, see Creating a Queue Processor rule.
  1. In Dev Studio, open an activity that is processed by the agent that you want to replace.
    Tip: You can enter the name of the activity in the Search field.
  2. Click +Add step.
  3. In the Method field, enter Queue-For-Processing.
  4. Expand method parameters and complete the fields according to your needs. For more information, see Queue-For-Processing method in the Admin Studio help.
  5. Click Save.
  6. Wait for the agent to process the items that this agent queues.
    Note: New incoming messages are queued and processed by the queue processor that you associate with the activity even before the agent resolves all its items.
  7. Disable a corresponding agent by performing the following actions:
    1. In Dev Studio, click RecordsSysAdminAgents.
    2. Select the agent that you want to disable, and then clear the Enabled check box.
    3. Click Save.
  • Previous topic Replacing an agent with a Job Scheduler rule
  • Next topic Replacing an agent with a Queue Processor rule for delayed messages
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us