# Enabling pyTransferAssignment Across All Harnesses

**URL:** <https://forums.pega.com/t/enabling-pytransferassignment-across-all-harnesses/10674>\
**Category:** Blueprint and App Design\
**Tags:** microjourney, customization, enterprise-application-development, financial-services, dev-designer-studio, cross-industry, customer-journeys, 24-2-3, workflow-automation, case-management, pega-platform\
**Created:** [February 8, 2026, 12:09pm UTC](https://forums.pega.com/t/enabling-pytransferassignment-across-all-harnesses/10674 "2026-02-08T12:09:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![VenkateshC17599704](https://avatars.discourse-cdn.com/v4/letter/v/858c86/32.png) [@VenkateshC17599704](https://forums.pega.com/u/VenkateshC17599704)\
**Post date:** [February 8, 2026, 12:09pm UTC](https://forums.pega.com/t/enabling-pytransferassignment-across-all-harnesses/10674/1 "2026-02-08T12:09:12Z")

</div>

In my application, I have configured the OOTB **pyTransferAssignment** local action as a case-wide local action. It currently only displays in the UI when the **newassign** clipboard page is available—specifically within an **assignment context** using the **Perform** harness.

The business requirement is to make **pyTransferAssignment** available across the case lifecycle, irrespective of the harness being used (e.g., **Review** or **Perform** ). Could you advise on how to implement this?

Additionally, is it aligned with Pega best practices to perform a transfer operation in the absence of an assignment context (i.e., transferring a case to another operator or work queue when no active assignment exists)?

Thanks,

Venkat Ch

---

<div class="post-metadata">

**Author:** ![Sairohith](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/sairohith/32/23362_2.png) [@Sairohith](https://forums.pega.com/u/Sairohith)\
**Post date:** [February 12, 2026, 3:58am UTC](https://forums.pega.com/t/enabling-pytransferassignment-across-all-harnesses/10674/2 "2026-02-12T03:58:02Z")

</div>

@VenkateshC17599704 Create a case-wide action (for example, Transfer Work) that runs a small flow to ensure an assignment context exists: first look for an open assignment on the case, and if none exists, create a short temporary assignment on the primary case. Immediately open the OOTB pyTransferAssignment local action on that assignment (so the newAssign page is present) and complete it to route the work to the selected operator or work queue. After the transfer, close or resolve the temporary assignment so it does not change the business flow. This makes the action usable from any harness because you always launch it through an assignment-backed step. From a best-practice standpoint, transferring without an assignment is not recommended because pyTransferAssignment is meant to move an assignment, not a case with no active work item.