Table of Contents

Creating a work queue


Only available versions of this content are shown in the dropdown

A work queue is a container that holds work that is waiting to be assigned to operators and robotic processes. Create a work queue so that work can be categorized prior to being assigned.

  1. In the header of Dev Studio, click Create Organization Work queue .

  2. On the Create form, enter values in the fields to define the context of the work queue by configuring the following properties:

    1. In the Short description field, enter text that describes the purpose of the work queue.

    2. In the Work queue field, enter a name that conveys the purpose and work queue contents to users of the application. Begin the name with a letter and use only letter, digit, ampersand, dash, @ sign, and period characters.

    3. Choose a name that can help application users and developers distinguish between work queues and operator identifiers. For example, each work queue can include "wq" as a part of the name.

      You cannot use pyBulkProcessing as a work queue name. This value is reserved for background bulk processing.
  3. Click Create and open to open the rule form.

    The ruleset name assists with application packaging and is not used for assigning work. To change the ruleset, click Edit at the top of the form next to the default ruleset name, and enter a new ruleset name or leave the field blank.
  4. Specify an organization, division, and unit. For more information, see Associating a work queue with an organization.

  5. Click Save.

  • Keystores

    A keystore is a file that contains keys and certificates that you use for encryption, authentication, and serving content over HTTPS. In Pega Platform, you create a keystore data instance that points to a keystore file.

  • Notifying operators of work queue activity

    You can configure a work queue so that specific operators are notified by email when new work is added to the work queue.

  • Copying a rule or data instance

    Use the Save As form to copy an existing record's functionality to a new record with unique key parts. This form is pre-populated with the original record's key parts and creates default values for the new record's context.

  • Creating a specialized or circumstance rule

    You can create a specialized or circumstance rule to create a variant of the rule that can be triggered only conditionally. The created rule is resolved and active only when the specified conditions are met. Create specialized or circumstance rules to address dynamic business requirements without changing the core logic every time. For information about rule resolution exceptions and how they might affect circumstance rules, see .

Have a question? Get answers now.

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