Skip to content

Commit bf0ada6

Browse files
authored
Fix broken link
1 parent 055e475 commit bf0ada6

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • content/en/docs/releasenotes/studio-pro/11

content/en/docs/releasenotes/studio-pro/11/11.8.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Maia Make capabilities are enabled by default. You can disable them in Studio Pr
4545

4646
- We introduced an opt-in runtime setting `MaxRetrieveAmount` that limits the maximum amount of objects retrieved by database datasource operation. (Tickets 236618, 247111)
4747
- We fixed the issue in OData Exists queries where an XPath constraint with nested-associations would result in incorrect OData filter (Ticket 261698).
48-
- We improved the new `reloadApp` function (explained in Other Improvements [above](#other-new-features)) in the `mx-api/ui` Client API to better handle sessionStorage quota exceeded errors. When `withState` is `true` and the browser's sessionStorage quota is exceeded, it now throws a `ReloadStateQuotaExceededError` that you can catch and handle. For more information, refer to the [Client API documentation](apidocs-mxsdk/apidocs/client-api-11/). When re-running an app in development and the sessionStorage quota is exceeded, the reload gracefully falls back to reloading without preserving state. (Ticket 264656)
48+
- We improved the new `reloadApp` function (explained in Other Improvements [above](#other-new-features)) in the `mx-api/ui` Client API to better handle sessionStorage quota exceeded errors. When `withState` is `true` and the browser's sessionStorage quota is exceeded, it now throws a `ReloadStateQuotaExceededError` that you can catch and handle. For more information, refer to the [Client API documentation](/apidocs-mxsdk/apidocs/client-api-11/). When re-running an app in development and the sessionStorage quota is exceeded, the reload gracefully falls back to reloading without preserving state. (Ticket 264656)
4949
- The `OQL DELETE FROM` statement now supports associations with [on delete](/refguide/association-properties/#delete-behavior) behavior with the following functionality:
5050
* Delete associated objects as well
5151
* Delete the object only if there are no associated objects

0 commit comments

Comments
 (0)