What is the difference between the data-admin-workbasket and embed-data-admin-workbasket?

General
,
1

Hi,

What is the difference between the data-admin-workbasket and embed-data-admin-workbasket?

Regards,

Mamatha

2

Hi @Mamatha Adiraju,

In Pega, both data-admin-workbasket and embed-data-admin-workbasket are classes used for managing workbaskets, but with a key difference in their purpose:

data-admin-workbasket:

  • This is the standard class for defining and managing independent workbaskets.
  • It represents a central pool of assignments that can be accessed and managed by various users or groups based on defined access controls.
  • Think of it as a shared in-box for tasks or work items that need to be distributed among users.
  • You can configure routing rules within flows to direct assignments to specific data-admin-workbasket instances based on criteria like urgency, skills, or workloads.

embed-data-admin-workbasket:

  • This class is designed for embedding workbaskets within another workbasket. It essentially creates a sub-workbasket within a larger one.
  • It provides a way to organize and categorize tasks within a single workbasket. Imagine a main workbasket for a department, and then embedded workbaskets for specific sub-teams or project types within that department.
  • Users with access to the parent workbasket can then access and manage the embedded workbaskets for more granular control over task distribution.

Here’s a table summarizing the key differences:

Feature data-admin-workbasket embed-data-admin-workbasket
Purpose Independent workbasket Embedded sub-workbasket within another one
Use Case Shared in-box for various users/groups Categorize tasks within a larger workbasket
Access Control Defined on the workbasket itself Inherited from the parent workbasket
Routing Can be routed to from flows Not directly routable, accessed through parent

In essence:

  • Use data-admin-workbasket for general workbasket creation and management.
  • Use embed-data-admin-workbasket when you need to create a hierarchical structure within a single workbasket for better organization and access control.

Regards,

Mohd Qizer Uddin

3

@Mamatha Adiraju,

DATA-ADMIN-WORKBASKET:
This is a concrete class in Pega that is used to define and manage workbaskets. Workbaskets are queues where work objects (cases) can be assigned for processing by operators or groups of operators. The data-admin-workbasket class holds the configuration and details of these workbaskets. This class contains properties that define the characteristics of the workbasket, such as its name, description, associated organizational unit, and routing rules. Instances of data-admin-workbasket are created to set up workbaskets that can be used in the workflow of various applications. These instances are typically created and managed through Pega’s user interface.

EMBED-DATA-ADMIN-WORKBASKET:

This is an embedded class in Pega, used to define a workbasket within another class or structure.
The embed-data-admin-workbasket class is used when you need to reference or include workbasket information as part of a larger data structure. It is not a standalone class like data-admin-workbasket, but rather it is embedded within other classes.
This class contains similar properties to data-admin-workbasket, but it is designed to be part of a composite structure. This allows you to include workbasket details within other data models.The embed-data-admin-workbasket class is used when you need to encapsulate workbasket information within other objects, such as when defining complex data relationships or nested structures in your application.

DIFFERENCES:

  • data-admin-workbasket is a standalone, concrete class used to create and manage workbasket instances. embed-data-admin-workbasket is an embedded class used to include workbasket information within other data structures.
  • Use data-admin-workbasket when you need to define and manage individual workbaskets. Use embed-data-admin-workbasket when you need to reference or include workbasket details as part of a larger composite structure.
  • data-admin-workbasket is for direct workbasket management, while embed-data-admin-workbasket is for embedding workbasket data within other objects.
4

Hi @Mamatha Adiraju,

In PEGA, data-admin-workbasket and embed-data-admin-workbasket are different rule types used for different purposes:

  1. data-admin-workbasket:

    • This rule type represents a workbasket in Pega. A workbasket is a virtual storage location where work items (cases) can be routed and stored for processing by users or agents. It typically includes properties such as the workbasket name, description, and access settings.

    Key features:

    • Defines the configuration of a workbasket.
    • Contains settings related to routing, assignment, and visibility of work items.
    • Used to manage and configure workbasket properties and behavior within the application.

  2. embed-data-admin-workbasket:

    • This rule type is used to embed a workbasket directly into a section or harness rule. Embedding a workbasket allows you to display the contents of a workbasket (such as work items) directly within a user interface component (like a section or harness).

    Key features:

    • Embeds a workbasket directly into a user interface component.
    • Allows for displaying workbasket content within a specific context, such as a portal or case manager.
    • Provides flexibility in how workbasket information is presented and interacted with by users.
    • Finally data-admin-workbasket manages the configuration of workbaskets at the system level, while embed-data-admin-workbasket integrates workbasket functionality directly into user interface components for enhanced usability and interaction.