Initial Work queues (Data-Admin-WorkBasket)
When initially installed, your system contains several work queues in the organization pega.com. These allow initial use of the system to create work items and assignments, but are not needed for correct operation once you set up your own organization and the equivalent work queues.
| Work queue | Purpose |
|---|---|
| [email protected] | Supports a development team the uses the optional Rule Management facility for check-in. See How to use the Rule Check-in approval process. |
| [email protected] | Work queue to be used as a last resort for routing, when no other more specific or local work queue can be found. |
| [email protected] | Sample work queue, for assignments that are not urgent. |
| IncompleteConnections | Supports the standard Work-.ConnectionProblem flow. See Handling Connector Exceptions. |
| [email protected] | Supports the standard Work-.RoutingRoles map value. |
| [email protected] | Not used. |
| [email protected] | Supports the standard Work-.RoutingRoles map value. |
| [email protected] | Supports a development team that uses the Rule Management facility for check in. See How to use the Rule Check-in approval process. |
| [email protected] | Supports the standard flow QualifyScannedDocuments. |
| [email protected] | Supports the standard Work-.RoutingRoles map value. |
As you create more organizations, create a work queue named
[email protected]
for each. Standard flow actions require a work queue with that name.
The standard map value
Work-.RoutingRoles
assumes the existence of work
queues named
[email protected],
[email protected],
[email protected],
[email protected],
[email protected]
and
[email protected], where org.com is
the organization of the current operator. If your application uses this standard map value,
make sure to create each work queue it references.
The standard flow
Work-.QualifyScannedDocuments
places work in a work queue
named
[email protected], where org.com identifies the Organization
data instance referenced by the Operator ID of the user who starts that flow. Create the
corresponding work queue before using this standard flow.