Atlas — Initial Workbaskets (Data-Admin-WorkBasket) |
When initially installed, your system contains serveral workbaskets in the organization pega.com. These allow initial use of the system to create work objects and assignments, but are not needed for correct operation once you set up your own organization and the equivalent workbaskets.
Workbasket |
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] | Workbasket to be used as a last resort for routing, when no other more specific or local workbasket can be found. |
[email protected] | Sample workbasket, 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 rule. |
[email protected] | Not used. |
[email protected] | Supports the standard Work-.RoutingRoles map value rule. |
[email protected] | R-9695 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 rule. |
As you create more organizations, create a
workbasket named default@org.com
for each. Standard
flow actions require a workbasket with that name.
The standard map value rule Work-.RoutingRoles assumes
the existence of workbaskets 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 rule,
make sure to create each workbasket it references.
R-6987 The standard flow
Work-.QualifyScannedDocuments places work in a workbasket
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 workbasket
before using this standard flow.
About Workbasket data instances
Atlas — Initial
Data Instances