UI Builder Workspace – Unable to Configure "Back to Story" Navigation When Task Opens as Sub Record

[HimanshuS876326]

Hi Everyone,

I'm building a custom Project Management Workspace using ServiceNow UI Builder and I'm facing an issue with record navigation.

I have three custom tables:

• Project
• Story
• Task

A Story references a Project, and a Task references a Story through a reference field (u_reference_1).

I have created three separate record pages in UI Builder:

• Project Record Page
• Story Record Page
• Task Record Page

The Story Record page contains the standard OOTB Record Related List Repeater that displays the related Tasks.

Problem

When I click a Task from the Story related list, I expect it to open my dedicated Task Record page. Instead, it always opens as a workspace sub-record under the Project Record page.

The URL is similar to:

.../project-record/.../sub/record/<task_table>/<task_sys_id>

Because of this, my custom Task Record page is never used.

Requirement

I need to add a "Back to Story" button while viewing a Task so that users can easily navigate back to its parent Story.

Current Situation

• A "Back to Project" button already works correctly from the Story page.
• If I place the "Back to Story" button on the Task Record page, it never appears because that page is never opened.
• If I place the button on the Story Record page, it is visible while viewing a Task (since the Task is rendered as a sub-record), but I cannot access the current Task record or its Story reference field to configure the navigation.

What I've Already Tried

• Used visibility scripts based on the current table (works correctly).
• Configured an Open Page event, but only Story fields are available for binding; Task fields are not exposed.
• Created a UI Builder Client Script and checked api.data, api.context, api.context.props, and event.payload, but none of them contain the current Task record.
• Checked the Form Controller, which only exposes the current table and sys_id.
• Created a dedicated Task Record page and added a Heading component to verify navigation. The heading never appeared, confirming that the Task Record page is never used.
• Checked the Record Related List Repeater configuration but couldn't find any option to override the navigation behavior.

My Questions

1. Why does the standard Record Related List Repeater always open the built-in sub-record page instead of my dedicated Task Record page?
2. Is it possible to configure the Related List to open a custom record page instead?
3. Is there any supported way to override the sub-record routing in a Workspace?
4. While viewing a Task as a sub-record, is there a supported way to access the current Task record (or its parent Story reference) from a UI Builder button or client script?
5. Has anyone implemented a Back to Parent Record button in this scenario? If so, what approach did you use?

Any guidance or best practices would be greatly appreciated. This is the final navigation requirement remaining in my workspace, and I've been unable to find a supported approach.

Thank you!