[MGNLRESTUI-7] BrowserSubapp, Select & Chooser should fail gracefully when Rest Datasource is offline Created: 12/Dec/19  Updated: 21/Jan/21  Resolved: 22/Jan/20

Status: Closed
Project: Magnolia REST Client UI
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Jorge Franco
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1h
Original Estimate: Not Specified

Attachments: PNG File image-2020-01-09-09-41-26-956.png    
Issue Links:
Problem/Incident
is caused by MGNLRESTUI-5 UI should fail gracefully when Rest D... Closed
causality
is causing MGNLRESTUI-11 DOC: Handling offline datasources Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes
Date of First Response:
Epic Link: Declarative REST clients
Sprint: Declarative REST 14, Declarative REST 15
Story Points: 8

 Description   

As an AdminCentral user, I want a simple message clearly indicating that some content is not available, so that I know what is happening in the system and know what to do.

Currently if a REST endpoint is not available (Thanks to MGNLRESTCL-76)  the content is not displayed and an error is written to the log, but the user does not know what happened or why.

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."

 

Acceptance criteria

  • Handle browser subapp (obstrusive)
  • Handle select box (non-obstrusive)
  • Handle link field (non-obstrusive)
  • REST supplier? —not an issue
  • (Did I miss a key UI element?)

Highlight dependency on UI improvement for fields if needed.



 Comments   
Comment by Christopher Zimmermann [ 07/Jan/20 ]

avongunten Could you provide suggestions for UI when link field or select field cannot load its contents?

Comment by Christopher Zimmermann [ 04/Feb/20 ]

Please add a comment describing how to use this feature, or what was done.

Comment by Jorge Franco [ 05/Feb/20 ]

The implemented behavior is the following:

 

  • If there is an error in a component using JsonDatasource, a Notification will appear (Obstrusive)
  • When using linkField, or comboBox, we have created two components in rest-client-ui (restLinkField and restComboBoxField). Using that components will check that rest calls are working properly, if there is an error with rest call a red label will appear and the component will be disabled. (non-obstrusive)
  • Error in rest search supplier will appear only in the logs.
Generated at Mon Feb 12 06:50:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.