In Agent Workspace the cursor randomly jumps from multiline field

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2022 08:00 AM
Does anybody experienced anything like this?
We have a multiline field on the Case table.
When the support engineeer types in this field in Agent Workspace, the cursor randomly jumps out from the field to somewhere else which is very annoying.
It started this behaviour after upgrading from Rome to Tokyo.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-22-2022 06:30 AM
This doesn't really seem to cover "the cursor randomly jumps out from the field to somewhere else which is very annoying." I'm seeing something very similar to BigZolo in the fact that my agents type a short description and then either tab or click into the long description and then the cursor jumps and makes a UI Action button "active" and if the agent doesn't notice right away and hits "space" it activates the button.
We are also seeing the jumping typing issue in the same field but a second issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2023 09:12 AM
Have you been able to find a KB for your issue? My customers are also experiencing what you've described
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-21-2022 08:12 PM
Not sure if this is your issue: when agent typing on some fields, workspace is auto-scrolling-up.
If yes, you can try create new variant of [record] route and use latest template [Standard Record]
-> set Order < your current variant to use this variant.
After that, replicate this issue to verify if issue fixed --> legacy template is not compatible with TOYKO.
If not, get a glance latest patch here
Hope this help!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-27-2023 03:54 AM
Our instances were updated to Utah Patch 4 Hotfix 2 on Friday 22nd June, and since then, our engineers have notified us of this same issue occurring again - has this happened to anyone else?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2023 11:53 AM
Noticing it currently on Tokyo Patch 9 Hot Fix 2