-
Story
-
Resolution: Done
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Declarative REST 12
-
5
As an AdminCentral user, I don't want to get giant red bars with cryptic exception errors when a connected REST endpoint is not available, because it scares me and does not help me understand why AdminCentral is not working.
Currently if a REST endpoint is not available an exception is thrown resulting in a big red error bar. This is at least true in a browser app, and is probably true in Select and Link fields or anywhere a REST datasource is used (Search results supplier?). (To verify)
UI elements that can have a REST Datasource should be able to gracefully handle the endpoint being unavailable. Probably showing a clear message where the content would normally be displayed - in the App, in the Chooser, in the Select field, etc. Something like "Content not available. Please try again later. If this problem persists contact your system administrator."
Maybe this needs to be solved in each UI element? Or maybe the REST Datasource can return a fake content item with the "Content service is not available" message.
- causes
-
MGNLRESTUI-7 BrowserSubapp, Select & Chooser should fail gracefully when Rest Datasource is offline
- Closed
- depends upon
-
MGNLRESTCL-43 Handle errors in a REST response
- Closed
- mentioned in
-
Page Loading...