This repository has been archived by the owner on Aug 30, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
Improve UI message, if no results are found #220
Comments
This was referenced Mar 12, 2018
Peym4n
pushed a commit
that referenced
this issue
Mar 20, 2018
As far as I can see their are two main cases left:
|
This message is shown when the widget cannot find a conversation ID or Smarti has no conversation for the ID, which means that at some point there might have been a communication problem between Rocket.Chat and Smarti. For now I changed the message to: "This room is not available in the knowledgebase!" In another case when no tokens exist while they are required, the widget will ask the user to add a search term (token) in order to get results. |
Peym4n
pushed a commit
that referenced
this issue
Apr 5, 2018
Peym4n
pushed a commit
to redlink-gmbh/Rocket.Chat
that referenced
this issue
Apr 6, 2018
ghost
removed
the
in review
label
Apr 20, 2018
mrsimpson
pushed a commit
to assistify/Rocket.Chat
that referenced
this issue
May 14, 2018
* Smarti-203: Flag widget messages * Smarti-203: Rename widget message flag to skipAnalysis * Smarti-52: Add support for edited messages * redlink-gmbh/smarti#221: Set room topic as support area for conversation * Revert "redlink-gmbh/smarti#221: Set room topic as support area for conversation" This reverts commit c7966a3. * redlink-gmbh/smarti#225: Fix widget footer styling * redlink-gmbh/smarti#220: Improve error handling * SmartiWidgetBackend: Improve error handling
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If no results have been found, the user should be informed friendly and readable.
There should be some more background information why, no results are being displayed and maybe the user should be linked to an article, that describes how to make use of the knowledge base (Smarti).
Moreover the loading animation should not overlap the text. Also it should disappear after the requests have been finished.
The text was updated successfully, but these errors were encountered: