Something that’s been driving me crazy is this error message that pops up when hovering over a C/R360 widget that you don’t have access to edit: “You do not have the required permission to edit the widget data. Please connect to your GS Admin.”
Why is this (grammatically dubious) message even needed? Also, it’s distracting because in this particular case, I have the widget linked to a related list report, so the end users need to click on the widget in order to quickly traverse to the related report. This is very slick and useful functionality but is partially ruined by the above message popping up every time. Please consider fixing this or at least giving admins the option to turn it off.
Yes please - the error here implies some unexpected issue with the system, when most of the time I’d expect this to be intentional on the part of the admin.
Yes - same problem (different area) as this idea:
Really don’t understand why the messaging is like this. Points for consistency but...not like this...
Ah thanks@bradley . Feel free to merge this, Gainsight Community team.
Ah thanks@bradley . Feel free to merge this, Gainsight Community team.
I don’t know, it would likely be fixed only in one place without a request for each area
Very much agreed. Your admin community didn’t request this messaging in the first place, so why was it ever added…? Completely unnecessary, and even worse, it adds additional confusion.
Oh my gosh, PLEASE get rid of this. It is unnecessary AND poorly-written. You’re making fools out of your Admins.
Yes, please stop those pop-ups.
If a field is not something they were supposed to have access to edit in the first place, all a prompt like this does is make them think they are supposed to have access but the admin forgot to enable it. Creates confusion and unnecessary outreach to admin.
cc:
Another thing that irks me about this, is that it also directly conflicts with any help text/description you add to a field or widget.
If I add a description, there is a TINY area I can mouseover to give me the description
But to see this giant block of text, I just have to hover anywhere over the value being displayed. Why would a useless message be prioritized over something an admin has specifically configured to aid the user in consuming information?
Make it easier for users to know if they can edit a field or not. Great, I have asked for this before (post appears to have been lost in the migration behind a Beta testing group wall) but this doesn’t do that, and if this were even the solution for it it doesn’t do it particularly well either. It’s just created another problem.
Agreed, this is kinda crazy.@rahul_prayakarao if you look at our instance, you will also see we have an HTML C360 Summary widget that shows essentially product icons. This shows the html upon hover, whereas we have actually designed it to show a sort of help text. This hasn’t worked since that recent release, and shows the whole long html instead. It’s nuts.
I’m even getting this when I hover over the standard Company>Name field. How did this get released@rahul_prayakarao ?
Every. Non-Editable. Field. On. The. C360. Summary.
Hello everyone. Apologies once again for the inconvenience caused to the CSMs. We’ve decided to remove the tool tip in 360 and revert to the previous experience.
Just to clarify, this change was part of a broader initiative (Field Level Permissions). We’re now separating the 360 Admin control from this, and the team will address it shortly (if everything goes as planned - in the next couple of weeks)
I’ll keep you updated in this thread as the changes are implemented.
Hello everyone. Apologies once again for the inconvenience caused to the CSMs. We’ve decided to remove the tool tip in 360 and revert to the previous experience.
Just to clarify, this change was part of a broader initiative (Field Level Permissions). We’re now separating the 360 Admin control from this, and the team will address it shortly (if everything goes as planned - in the next couple of weeks)
I’ll keep you updated in this thread as the changes are implemented.
Glad to hear it will be reverted. I would encourage the team to test these out with actual users before releasing them to see if they make sense in real world scenarios.
Glad to hear it will be reverted. I would encourage the team to test these out with actual users before releasing them to see if they make sense in real world scenarios.
I cannot
this enough!