Hi all,
Are any other RAMP users having issues typing into Tessitura?
We've been experiencing issues for a couple weeks now where some users cannot type anything into any search fields or there is a massive delay while typing or copying and pasting into these fields. For me, I am experiencing these issues in the pricing layers.
We currently have a ticket open but I wanted to learn if anyone else who is hosted on RAMP is having the same issue and if it is ongoing or if it was resolved?
- Chris
Despite these issues ONLY happening in Tessitura, Tessitura believes this does not appear to be a setting or configuration issue on the side of Citrix/the hosting environment.
Good luck!
We thought for a while that this was related to getting on the latest version of the client on Macintosh. However, that has not fully resolved the issue. One of the support team members did some cleaning out of the configuration files on my account which may have helped. However, my problems are back again.
In our case key causes of the problem are turning out to be switching from 1 monitor to 2 monitors and back on a laptop without first fully shutting down Tessirutra RAMP. It's almost like the citrix window positioning is way to sticky for our scenario. Where I could imagine that this window position stickiness is a feature for some others who don't change there setup as often.
Basically the same thing here. It is like Windows is not fully recognizing that you have selected the Tessitura application as the application on which you are working. It clearly has selected it partially, because if I keep typing, it does not keep typing in, for example, Word or Notepad if those were the previous applications I was using. However, it will often not start typing in Tessitura until I go to the taskbar at the bottom, and intentionally select the Tessitura application rather than just clicking in the application window itself.
Irritating, yet now that I know how to solve the issue, at least less of a true issue.
Since we upgraded to Version: 15.1.1, this has no longer been an issue for us.
Upgrading to Version: 15.1.1 seemed to do the trick for us.