Initial Workbaskets (Data-Admin-WorkBasket) |
When initially installed, your system contains several workbaskets 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 workbaskets.
Workbasket |
Purpose |
| CheckInCandidates@pega.com | Supports a development team the uses the optional Rule Management facility for check-in. See How to use the Rule Check-in approval process. |
| default@pega.com | Workbasket to be used as a last resort for routing, when no other more specific or local workbasket can be found. |
| deferred@pega.com | Sample workbasket, for assignments that are not urgent. |
| IncompleteConnections |
Supports the standard Work-.ConnectionProblem flow. See Handling Connector Exceptions. |
| inprogress@pega.com | Supports the standard Work-.RoutingRoles map value. |
| QA@pega.com | Not used. |
| requests@pega.com | Supports the standard Work-.RoutingRoles map value. |
| ReviewChanges@pega.com | Supports a development team that uses the Rule Management facility for check in. See How to use the Rule Check-in approval process. |
| ScannedDocuments@pega.com | Supports the standard flow QualifyScannedDocuments. |
| support@pega.com | Supports the standard Work-.RoutingRoles map value. |
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 Work-.RoutingRoles assumes the existence of workbaskets named requests@org.com, inprogress@org.com, deferred@org.com, Administrator@org.com, support@org.com and default@org.com, where org.com is the organization of the current operator. If your application uses this standard map value, make sure to create each workbasket it references.
The standard flow Work-.QualifyScannedDocuments places work in a workbasket named ScannedDocuments@org.com, 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.