> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release7.2/hotfix-releases/release7.2.5.x/release7.2.5.30.md).

# Release7.2.5.30

This release introduces a bug fix in Data Stories, improving link reliability and ensuring seamless access to customized Data Catalog views.              

**Key Highlights**

* **Data Stories**: Fixed broken links to customized Data Catalog views by preserving the complete URL when links are added to Data Stories, allowing the views to open successfully from both Data Stories and Home Page Stories.  

**Release Details:**

<table><thead><tr><th width="132.111083984375">Release Type</th><th width="143.99993896484375">Release Version</th><th width="344.0001220703125">Build&#x3C;Release. Build Number. Release Stamp></th><th>Build Date</th></tr></thead><tbody><tr><td>Patch Release</td><td>Release7.2.5.30</td><td>release7.2.5.30.72530.f8fe3f9</td><td>September 18, 2026</td></tr></tbody></table>

## Data Stories

### Fixed

**Resolved Broken Links in Data Stories**&#x20;

In Data Stories, an issue where links to customized Data Catalog views were truncated when added to a Data Story has been resolved. The incomplete links resulted in a 400 – Link Broken/Not Found error when accessed from the Data Story or Home Page Story.

The link handling has been corrected to retain the complete customized Data Catalog view URL, allowing the link to open the corresponding view successfully.

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release7.2/hotfix-releases/release7.2.5.x/release7.2.5.30.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.