Bug on new request list experience (Beta)
回答済みMy company is trying to implement a new request list experience on Guide, however we have found bug that potentially prevent the change to be promoted to production.
When we enabled this beta experience, end-users are able to filter-up custom fields to be displayed on the column.
Let's say that I have a custom field, that is not visible for end-users below:
On the end-user's view in Guide, the user would still be able to query up this field:
Then the column will be displayed on the frontend, even the value of the fields are not actually being displayed (There are actually values in the field, but those are visible as blank for the end-users):
Ideally the fields that are not visible for the end-users should not be visible when selecting to 'show' or 'hide' the column.
Could someone having a look at this bug so that we could deploy the change without affecting the customer experience on September?
Thank you.
Tanawat
-
Hey Tanaway,
I believe I found the issue some time ago. When logging in as an admin and then assuming access as an end-user it looks like somehow cached cookies or information may still be utilized in the list that the agents can view. The only way I could view only the customer-facing fields was to log in on a test account in our Production instance in an incognito window. Any time I logged into a normal browser or incognito browser first with my normal admin account and then went to assume a user additional fields would be populated.Regards,
Spencer Barrett -
Hi Spencer,
This is actually true, tried incognito with the actual signing in with end-user's id/pw and do not see the fields, thanks for the recommendation!
-
Thank you for bringing this up.
Just to confirm what Spencer Barrett writes, no fields are being exposed to users that would not already have access to them, but team members are able to see fields they would have access to in Agent workspace and this also happens with assumed end users like Spencer mentions.
サインインしてコメントを残してください。
3 コメント