We have a requirement from the user to show only parent case assignments and hide child cases and its assignments. Any thoughts how to achieve this in constellation application.
@GangadharY17544252 What is the reason behind this stated requirement? A child case is inherently related to its parent, and so should make sense to relate when viewing the parent. Perhaps your situation warrants creating the child case as its own top-level case instead?
I would start by thinking about the work setup, if a child case setup makes sense or not. Considering especially if the flow in the child case is really related work to the parent or if it in reality is its own standalone workflow that the parent doesn’t depend on.
@LantzAndreas exactly
Hiding assignments of child cases | Support Center, examples of others that came to same conclusion as this
@GangadharY17544252 the assignments section of the UI is not authorable, its a prescribed design component.
We do have feedback on our backlog to make this more authorable. However, if the child case is not really apart of the hierarchy and should not be seen, you can use things like “spin-off” or top level case creation and/or related cases to create a more appropriate case hierarchy model.
@MarcCheong @GangadharY17544252 To add to Marc’s image above, here is an article on our docs that guide you on how to link the cases together by case reference when you create them, even when they are not child cases but top-level cases.
@LantzAndreas additional advise when you use a spin off case is to populate a case reference field so that you can use this to navigate easily from originating case into spun off case(s) and the other way around. Just like the OOTB pattern of creating cases from a data record (in the data type actions tab in app/dev studio) which automatically connects the newly create case to the data record it was created from (through a data reference field). I have reduced my use of child cases significantly since i have adopted this pattern.