Possibility to customize the Project Workspace RIDAC to show the RIDAC records from sub-projects

[rahulpanwar]

Hi Community,

What are the possibilities to customize the RIDAC page on project workspace? Currently it shows the RIDAC records created on project, but we have project and sub-project structure and we want to see the RIDAC records from the sub-projects on top projects.

Showing Top task's Risks, Issues, Decisions using relationship is possible but it shows all records in different tabs. So, if there is any OOTB approach to customize RIDAC page to show top task records, that will be great.

Thanks & regards,

Rahul

[Matthew_13]

Hi my Friend

 From what Ive seen, there really isn’t a true OOTB way to change the Project Workspace RIDAC tab so that it automatically rolls up Risks, Issues, Decisions,  from sub-projects into the top project view.

Out of the box, the RIDAC page is scoped strictly to the current project/task. Using relationships or Top Task does work, but as you’ve already noticed, it splits everything into separate tabs and doesn’t give you a single consolidated RIDAC view.

The only semi-OOTB option is relying on related lists/relationships to surface child records, but that still won’t behave like the native RIDAC page and won’t unify everything in one grid.

In practice, most teams handle this with customization:

• Create a custom tab in Project Workspace UI Builder that queries RIDAC records for the current project and its child projects.

• That tab can look and feel like the RIDAC page, but uses parent/child logic in the data source.

• This is currently the cleanest and most flexible approach if roll-up visibility is a hard requirement.

So what I see unfortunately, no supported OOTB toggle or setting exists to do this on the existing RIDAC page. If leadership wants top-level visibility across sub-projects, a custom Workspace tab is the realistic solution.

@rahulpanwar - Please mark as Accepted Solution and Thumbs Up if you found Helpful!!

[rahulpanwar]

Thanks for the response @Matthew_13, I liked the idea of adding a separate page with custom approach to show the rolled up records.

I also tried customizing the "getRIDACData" function on "RIDACWorkspace". For Risks, instead of task, if we query top_task, it will show the Risks of sub-projects. Currently we are analyzing, if any challenge with this approach.

[Matthew_13]

That’s a good direction, and your thinking makes sense.

Using a separate custom page to show the rolled-up RIDAC records is definitely the safer approach long-term, especially from an upgrade and support perspective.

Your idea of adjusting getRIDACData to query by top_task instead of task will work functionally, and it’s a common way to pull in Risks from sub-projects. The main things I’d keep an eye on while you’re testing are:

• Upgrade impact – if RIDACWorkspace is OOTB, changing it directly could get overwritten during upgrades. Cloning or extending it is usually safer.

• Scope and accuracy – make sure the top_task logic doesn’t accidentally pull in records from unrelated hierarchies or historical re-parenting.

• Performance – rolling up sub-project data can significantly increase the number of records returned, so watch for load time or pagination issues.

• Consistency – if Risks are rolled up using top_task, users will expect the same behavior for Issues, Decisions, Actions, etc.

• Access control – confirm users are allowed to see RIDAC records from sub-projects, otherwise you may expose data they shouldn’t see.

Overall, your approach is valid — just treat it as a controlled customization and test carefully. If you can keep the roll-up logic isolated (either in a cloned page or a custom component), you’ll be in a much better place when it comes to maintenance and upgrades.

@rahulpanwar - Please mark as Accepted Solution and Thumbs Up if you found Helpful!!