- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2023 04:01 PM
Has anyone had any problems with editing their favorites in the Next Experience UI?
Sometimes the drag and drop functionality just stops working for some users and returns for an unknown reason. I've been unsuccessful in trying to reproduce this problem, but I have experienced it. It seems switching browsers solves the problem, but I would like to know if anyone knows more information about this.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2023 05:07 PM
Hi kwong43,
Thats good to know. We previously faced another issue on PRB1639249 which was fixed in Patch 2 or 3, so I am looking forward to this stabilizing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2023 04:25 PM
Yes, I have had problems editing favorites to either add a favorite to a freshly created group or to reorder one. I have created HI tickets but been unable to reproduce live. I think the problem is when you do more than one thing (or multiple things) in the same edit session. Like if you create a group and do a reorder. So as a workaround I do one thing and exit the reorder and that seems to be a more stable experience for me.
I am still working on a recorded demonstration of my problem state as well as a repeat by and when successful will open a new support ticket.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2023 04:54 PM
Hi VL10,
I found KB1364734 - Intermittent issue with favorite drag and drop, in the ServiceNow Support Issues.
It is seen in Utah Patch 5, and the intended Fix Version is Utah Patch 7.
It's good to know this is a known issue!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2023 05:07 PM
Hi kwong43,
Thats good to know. We previously faced another issue on PRB1639249 which was fixed in Patch 2 or 3, so I am looking forward to this stabilizing.