Restricting access to Parent Case from Child Case in Pega Constellation 25

User Experience
1

Hi all,

I have a requirement to prevent users from accessing the parent case from a child case.

I removed permissions (Open, Modify, Run reports, View audit history) on the parent case via Persona configuration, but then the child case fails to open due to missing access to the cover case.

If I enable Open, the error is gone—but users can open the parent, which I want to avoid.

Constellation requires parent case access for runtime/context resolution.

Is there a recommended way to restrict parent case navigation (UI/behavior level) without breaking child case access?

Any best practices or workarounds would be appreciated.

image
image443×156 19 KB

2

I think if you have different personas responsible for parent and child cases, then you can implement ABAC access to restrict the access. The child case personas can’t read parent case if you have restrict Read policy.

3

I’ll try to do in this way.

Thank you.

4

You could also break the child/parent relationship.

When I’ve had this use case in the past, we use features like Related Cases or even a Case Reference field on the cases to form a “dotted line” link between them, rather than the harder Parent/Child provided when you create child cases.

5

Thanks @MarcCheong

It’s a very good idea. The challenge is that I already have the full implementation based on a parent–child relationship. I’ll need to evaluate whether breaking this relationship would require significant effort.

Thanks a lot for suggesting this approach.

6

Effort would depend on what has been done so far:

  1. The create case shape, from dev studio, allows for simple change from “child case” to “case”
    1. It also has a property to store the originating case in (previously parent)
    2. image
      image1092×514 31.2 KB
  2. So then its just a matter of finding any mention of “cover” or the parent case in your other logic
  3. You’d also have to look at the parent case resolution
    1. image
      image346×283 9.55 KB
  4. And also if you have any wait shapes waiting for child cases - that is harder if you break that parent/child link
    1. image
      image589×383 15 KB
  5. Finally there would be your case views - showing a link between them and hiding that link if you didn’t want certain persona’s to see them

You are right to be cautious, its not a simple switch over by any means. However, it would give you more control over the breadcrumb trail and access :slight_smile:

let us know how you go!

7

Thank you again for your detailed response @MarcCheong

I have been considering switching from a child case approach to a related (non-child) case. However, the main challenge is that I need to create multiple cases based on a list.

In the parent case, users select a set of items, and for each selected item, a new case must be created. When using the Child case option, there is a built-in capability to handle this scenario through “Create multiple cases using a list.” Unfortunately, this option does not seem to be available when creating regular (non-child) cases.

image
image300×350 11.7 KB

Is there any way to support creating multiple non-child cases from a list, similar to the functionality available for child cases?