In Case Management framework, Case_GetActivities only returns case activities, not every BPT Human Activity that happens somewhere inside your processes.

That distinction is the reason you only see “top level” items and nothing from inside your “Execute Process” / subprocess levels:

• Activities that are explicitly modeled as Case Activities (using the CMf patterns) are exposed to Case_GetActivities.
• “Plain” BPT Human Activities that live inside your business process (main process, subprocess, “Execute Process” patterns, etc.) are not exposed as CMf activities and therefore will not appear in Case_GetActivities.

This is by design; BPT runtime / BPM tables are not meant to be queried directly from application code, which is also why an Advanced Query cannot reach them.

How to make deeper-level work items visible

To list work that is happening “deeper” in your process, you have to surface it as case activities. Typical approaches are:

1. Create a dedicated Case Activity representing the work you’re doing inside the subprocess, and:

   • Start that Case Activity when your “Execute Process” starts the corresponding BPT Human Activity.
   • Assign the Case Activity to the same user/group you assign the BPT Human Activity to.
   • Complete/close the Case Activity when the BPT Human Activity finishes.

   Once it’s a proper Case Activity, Case_GetActivities will return it (and you can filter/assign using ActivitySearchCriteria as in the example for user and group assignment). Really mine with Case_GetActivities

2. Use subcases/subflows instead of deep subprocesses when you want the case engine to understand the structure.
   In CMf, a common pattern is:

   • Main case flow is “waiting” on a subcase/subflow.
   • The subcase contains its own Case Activities.
   • Those activities naturally appear in Case_GetActivities, while the parent case waits. Case Assign Process, after subprocess

In both patterns, the key idea is: if you want to see something in Case_GetActivities, model it as a case-level activity or subcase, not just as a BPT Human Activity buried inside a process.

Why you can’t just query BPT directly

As you mentioned, Advanced Queries can’t hit BPT meta-model tables; those are only accessible via:

• Built‑in BPT meta‑model aggregates (when you expose process entities), and
• BPT APIs (e.g., Human Activity Assign To User), which are intended for programmatic control of processes, not for building taskboxes/UI. How To Use APIs to Programmatically Control a Process

So, for building your Taskbox in CMf, the supported way is to surface everything you need as Case Activities and then rely on Case_GetActivities plus its search criteria to retrieve those.

Bottom line: there isn’t a configuration or parameter of Case_GetActivities that will suddenly expose Human Activities hidden inside “Execute Process” levels. You’ll need to refactor so that the work you care about is represented as CMf Case Activities (or subcases) that mirror the inner process activities.