Is It Expected Behavior That Assignments Opened from a Work Basket Do Not Move to the User Worklist in Pega Constellation?

User Experience
, ,
1

Hi Everyone,
In Pega Constellation, even after a user opens an assignment from a Work Basket and clicks the Go action to start working on it, the assignment continues to remain assigned to the Work Basket rather than being reassigned to the current user.

Why does the assignment not automatically move from the Work Basket to the user’s Worklist when the user starts working on it in Constellation?
Can this behavior be confirmed as expected and by design?

2

Hello @Mohamed_Siddiq_N

Yes, this is expected behavior in Constellation and by design.

Clicking on Go button only opens the assignment for processing and it does not imply ownership transfer. An item in a Work Basket is considered unassigned, and Constellation intentionally separates opening (UI action) from assignment (business routing decision). This avoids accidental ownership, race conditions, and locking issues when multiple users access the same queue item.

If you want the assignment to move to the user’s Worklist, it must be done explicitly, for example:

  • Use Get Next Work (auto-claims before opening)
  • Provide an “Assign to me” action (MoveToWorklist)
  • Or implement custom logic to assign first, then open

Recommended approach is a hybrid pattern:

  • Go – view/work without claiming
  • Assign to me – explicit ownership
  • Get Next Work – auto-claim for efficiency

So, the behavior you’re seeing is correct and aligns with Constellation’s design principles.

Hope this helps.

Regards

JC

4 Likes
3

Can agree with every point made by @JayachandraSiddipeta. Also note that if you’re working with principles like Get Next Work or Assign to me there are some caveats:

  • If the assignee changes from a WorkBasket to a WorkList, different ARO’s might be triggered
  • If Assign to me is chosen, the requestor that continues assignment processing may not end up being the requestor you’d think you’d have (for example, after background processing). Case routing to work parties is, in my experience, the more reliable choice.
3 Likes
4

@Mohamed_Siddiq_N this has always been the Pega behaviour. Unless you customised the behaviour or the buttons, ownership was not transferred by just opening an assignment.

Ownership and work allocation should always factor into your design (some great options above)

1 Like
5

@Mohamed_Siddiq_N are you in the User Experience Expert Circle? I would like to move this under that area, so it can be found with other Constellation questions. However, if you are not a member you won’t be able to respond (until you join), so don’t want to just move on you.

Please let me know if you join and i’ll move.

6

Hi @MarcCheong
yes — I’m already a member of the Expert Circle.
Please feel free to move this thread under the User Experience Expert Circle section.

Thanks!

1 Like
7

done :clap: thanks! good to keep content together in one place for future