>

25.2 – Screen Jumps After Clicking “Apply Changes” When Saving New Function Line

Answered
Akash Satalkar
Edited

Comments

14 comments

Date Votes
  • Nicole Loh

    I remember that the fixing of line jumping was for continuously function scripting one line after the other without saving. There was also case APP-4308 and APP-5033 where it resolved some cases related to function positioning when returning from screens like add service order. Your case is slightly different in the sense that clicking on “Apply Changes”, the line will lose the positioning of the newly added function line. 

    Please see example in QE25.2: 
    1. Log in to https://qe.ungerboeck.com/25_2/app85.cshtml with nicole // nicole
    2. From the navigation menu, click on Events. Search for event ID 64164. 
    3. Navigate to the Functions Tab. 
    4. Right click on Catering (which is the second line from the top) > It should add the line after a level 3 - Catering 2.2 line. Click on Apply changes. 
    5. Notice that after it saves, it scrolls up a little and I lose the positioning of my new function line that I have just added. 

    If you add any new lines at the bottom half of the function scripting lines, it does the same thing. 

    Birdie recording: https://share.birdie.so/o/QjAiRKZp 

    I have also tested on 24.3 and 24.4 (classic UX) and the behaviour is the same. I want to say that it currently the expected behaviour of the system and what the customer is asking for would be considered an enhancement. I am on the fence on this one. 

    Cathy Herrick and Mike Schepker Have you had this scenario before? I can see the benefit of it entered as as bug, but the classic UX is also behaving the same (which might lean towards this being an enhancement). 

  • Mike Schepker

    Nicole Loh Based on your video, I think I concur that it probably is working as designed, but that doesn't mean it still isn't confusing. 

    I think I can see the software logic in my head as to why it's doing what it's doing but as an end user, that's not what I'd expect to see, if that makes sense. I honestly don't work with functions much, so I haven't run into any customers reporting this myself. 

  • Carissa Harrison
    Edited

    They probably have word wrapping enabled in their view. Word Wrapping is notorious for causing jumpiness even in classic UX. Try disabling this. 

    There is a lot of business logic the grid has to filter through upon reload too. We've made improvements as best we could to address this throughout the years, word wrapping is typically always the culprit and alleviates most of the jumping. 

    You can input this as an enhancement. 

  • Akash Satalkar

    https://app.pendo.io/s/6229449325477888/listen/feedback/views/ZWNAnL_3nsJ6p5EtfWhAOeEO8vg/items?openItem=pCPdguTULzEf9tp97PcizltyvPQ

  • Caroline Grzesniak

    Hi Carissa Harrison and Seth Halvaksz . The customer does not believe this is an enhancement request, but rather an issue stemming from a change on our end.

    Their users confirmed that the jumping issue was resolved after upgrading to version 25.2 on July 28th. Importantly, they did not disable text wrapping after the upgrade.

    The issue reappeared only after the Bad Gateway Error Ticket 364430 (https://ungerboeck.zendesk.com/agent/tickets/364430) was resolved on August 6th. Given this timeline, they would like us to further investigate the matter. Could we please re-examine the issue with this context in mind? The customer is dissatisfied with the enhancement request approach.

    Thanks for your help.

  • Seth Halvaksz

    Did they try disabling word wrap as Carissa suggested?

  • Caroline Grzesniak
    Edited

    Hi Seth Halvaksz yes they have.

  • Seth Halvaksz

    Caroline, i'm confused. You said in your previous comment:

    “Importantly, they did not disable text wrapping after the upgrade.”

  • Caroline Grzesniak

    Hi Seth Halvaksz  - they never disabled the text wrapping after the upgrade and it was working fine. Our team then actioned ticket #364430 and it was no longer fine. They turned off text wrapping to test, and this did not fix the issue. They as a business require text wrapping to be on, however.

  • Seth Halvaksz

    Thanks for clarifying. The grid is incredibly complex, and i'm told this also happened in classic but perhaps not as often.

    The change in ticket #364430 could be coincidental.  I see it was a change by the cloud team (this was not a software change).  I'm not sure exactly what was done from reading the ticket.  I'm assuming this was just a server-side update, they didn't patch (if it was a patch then that would be a software update).

    Maybe we schedule a time to test reverting the change in #364430 to see if that resolves the problem. Then that would confirm if that caused the problem. Then we get a call going to troubleshoot.

    Also, are your other customers complaining about this? I am surprised we aren't hearing from other customers.

  • Caroline Grzesniak

    A test reverting the change would be appreciated - please let me know what I can do to facilitate this so we know for sure.

     Akash Satalkar is aware of some similar themed issues.

  • Seth Halvaksz

    Akash Satalkar it looks like Satya Ram Nukala worked on ticket #364430. Could you reach out to him to ask for what change was made, and if it could be temporarily reverted to test if that resolves the issue?  If it does then we can troubleshoot why that change causes this.

  • Satya Ram Nukala
    Edited

    Seth Halvaksz Re:364430 The only thing SRE did was increase the space in the server to resolve that issue.  I don't think it will break the Function grid! 

  • Seth Halvaksz

    See the comment from Caroline that everything was ok before that ticket. They would like to try disabling temporarily to confirm whether it was the cause.

Please sign in to leave a comment.

Didn't find what you were looking for?

New post