Best practice - Case content task component or Hierarchal table?

I need to view assignments (priority), sub cases and resolved child cases (Parent and relative Child cases) in the ‘Case screen/Case content’ UI.

In Retail lending manager Pega 7 and Product Application Pega 7 the app utilise the Case contents (table) that shows Cases and Open assignments (in hierarchical order) . In Pega 8 What’s best practice should we use old (legacy) hierarchical table for Case contents ?

Problem statement: The Task components displays (RDL) a list of assignments and subcases for the current work object. However, it doesn’t display the resolved child cases and Hierarchal list view unless we customise. (see Child cases listed in parent cases)

Can you answer these Q’s"

Note: The OOTB section has legacy markup checked, which mean its not optimized. Will this be supported by product team in future ?

@Michaelw1090 this is quite an in-depth question. Below some information obtained by our GenAI documentation and forum search:

  1. The Task Component is the best practice and future-proof.
  2. Task Component is modern and customizable but requires customization for resolved child cases. Hierarchical Table is legacy and not recommended.
  3. leverage the new feature to list child cases in the parent case view.
  4. . Customization is needed to display resolved child cases in the Task Component. Legacy markup is not optimized and may not be supported in the future.

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

What’s new in Case Management > Child Cases list in the parent Case View

Best practices for managing interactions between parent and child Cases