Hi team! I am using Thoughtspot Embed
Hi team! I am using Thoughtspot Embed SDK to embed Liveboards into our app, and I was curious if there was a way to hide Error details that show specific information regarding our database like the name of the database, who it was created by, when it was created/modified, the datasource, etc. It seems like the "Last modified by" is "Not displayed because of permissions" and I was curious if that was something we can do with the other variables. Examples posted. Thanks!
18 Replies
I will have to check internally on this. Although can you check if you can handle errors with this : https://developers.thoughtspot.com/docs/events-app-integration#use-cases
Events and app interactions
Events allow the embedding application to send and receive messages from embedded ThoughtSpot components.
Looks like we cannot modify it using any TS app configurations, we might have to handle it either using the error events or in your code. Though I will raise a feature request for this internally to be able to configure error fields and such.
Hey @shikharTS ! Regarding those error events - would it be possible to use them to block the errors themselves? Or is that something that we will need as a feature request? We want to make sure we hide these things from the user - potentially instead just showing "Internal Server Error" or such.
Hey @shikharTS ! Any updates on this? Thank you! 🙂
I think you will need to raise a feature request for this. Also will let @utsav.kapoor / @jbc comment here if that is possible through some workaround
@Connor Craig - Can you create a feature request. This doesnt have any workaround
Hey @shikharTS ! We were thinking of using CSS to potentially hide these buttons - do you know if some of these CSS rules could cause issues elsewhere in the Liveboard embed?
muted-alert-module__actionButtons we want to set this one to display: none basically hiding buttons that allow users to display details of error message. We also want to hide Go to Home buttons or Report buttons. Was wondering if you know of anywhere else this could affect?@Connor Craig - This will cause issues in other places in embed. The classes for this will affect other alerts as well as dialog boxes
Is there any way we could use CSS to block those buttons? I think it's okay to hide the alert buttons, since all of them just are used for showing additional details of the error,
Go to Home, Report, etc. Any others that might be necessary for the user?
@utsav.kapoorI think that is correct. You can hide muted alerts button. I just checked the code on that area. This will hide action buttons and not hide error description which is useful in debugging
I would just be extra cautious with dialog buttons as that will have a larger impact on liveboard embed
Any idea what sorts of dialog buttons that would affect?
muted-alert-module__actionButtons will not affect any dialog buttons.
In the screenshots that are shared above, we see buttons on the error dialog box, I was referring to that for being extra cautious
Ah okay. Users I think won't be able to open those dialogs once we hide the buttons anyhow to open them 🙂
Thank you!
No Problem. Let me know if you need any other help 🙂
Hey team! Do you know what
suppressErrorAlerts does on the Thoughtspot Liveboard embed in the init function? It seems like it might suppress the errors that are coming up in the Liveboard but that doesn't seem to be the case. Any idea if this is broken?
We also created a feature request for this so that we can have a more permanent fix instead of CSS https://community.thoughtspot.com/customers/s/idea/087Uk000000TIO9IAO/detailI think that just might be for errors which cause alerts within the app, producing red banners (which is an error alert in TS app), not the functional errors in business logic..
Ah okay, I'm unsure much what that means - could you give an example of an alert within the app that this blocks?
From the code I see the alerts that this flag suppresses are :
1. CSP_VIOLATION_ALERT
2. No cookie access alert
3. Duplicate token alert
Looks like these might mostly be related to auth errors, but errors generated by the application's business logic are not suppressed by these..
Ah okay, thank you!