Hoppa till huvudinnehållet

Lagging while loading form on mobile

Kommentarer

11 kommentarer

  • Phil MacIntyre

    Hi Aaron,

    Hi Aaron Wong the website is currently migrating:

    https://community.vertigis.com/hc/en-us/community/posts/11403621847442-Migrating-to-the-VertiGIS-Global-Support-Platform

    Edits appear to still be fine but we're expecting some interruptions in the next day or so while this is underway. If you would like a faster resolution, you might try firing an email into our Support team for further troubleshooting. Otherwise I'll check back in once things have stabilized a bit more.

    Phil

    This is Phil from the Mobile team. My first two questions would be a) how large of a form have you created, and b) what sort of iPad are you using? We've seen before that rather large forms (e.g., say 3-5 or more screens' worth of scrolling with dozens of form elements) that you can get some UI-flickering and slow down, which is exacerbated by older/less powerful hardware.

    A few suggestions that could help improve your experience would be:

    - split your form out into multiple display form pages. Rather than one giant page with dozens and dozens of options, you could make it into 3-4 logically grouped pages. This can also make for a nicer experience for your users as they're not having to scroll as much

    - make use of collapsible sections. Workflow offers both standard collapsible sections as well as the new 'accordion' sections (where only 1 per grouping can be open at a time). This will also reduce the amount of content displaying at once

    - hiding/showing form elements as needed. Same sort of idea as above, just dynamically reducing the current display load within the form without using multiple pages or sections

     

    Hope that helps!

    Phil MacIntyre

    0
  • Aaron Wong

    Thanks Phil.

    That's kinda what I thought but just wanted to confirm with someone.

    Also just checking out Accordion.. wow that's neat.

    Thanks a lot!

    0
  • Aaron Wong

    Update 

    Tried using collapsible sections (Client's environment is 3.25 so Accordion is not available). But the same performance issues are noted. 

    Will Accordion help? or splitting them into different forms is the safest bet? or do we need to hide the elements when the section is collapsed? 

    0
  • Phil MacIntyre

    Hi Aaron,

    Collapsible and accordion are essentially the same, the only difference being that accordion sections only allow one to be open at a time. If using collapsible sections, while many of the elements are collapsed, doesn't help, I wouldn't expect accordions to make a difference.

    Splitting them into separate forms might be your best bet. What sort of hardware are you testing against? How many elements/how much data are you trying to pack into a single form?

    Phil

    0
  • Aaron Wong

    Hi Phil,

    Just to clarify, if many of them are collapsed it wouldn't work? I would expect less items opened would work better.

    We are testing it on a ipad 7th gen and an ipad pro 2020. 

    The form we are having the most issue on has 10 sections, each has 4 elements (2 dropdowns and 2 texts). And a changed event setting feature attribute on each of those.

    We have 3 other forms that are essentially doing the same thing, they have 3, 2 and 8 sections respectively. 

    Thanks,

    Aaron

    0
  • Phil MacIntyre

    Hi Aaron,

    Yes, you're correct. If the sections are collapsed I would expect it to be a bit more performant than if they were open.

    That hardware sounds reasonable for Go; I would in particular expect good performance out of the Pro model.

    That size of form sounds about right for the issues you're describing. We've made some improvements in our last several releases around form optimizations, but unfortunately one of the third party libraries we use is still causing us some issues. We'll continue to work to improve our forms, but for the moment I think breaking your form into a few separate forms might be your best bet to prevent the responsiveness issues.

    Cheers,

    Phil

    0
  • Nico Burgerhart

    Could it be related to the Change events?

    0
  • Phil MacIntyre

    Hi again Aaron,

    The Communities migration has been complete and comments are once again enabled. I've done a simple test, spinning up a Workflow similar to what you've described, just without any change events, and confirmed that works totally fine on all of my various test devices (Android, iOS, and Windows). No lagging, no UI flickering, nothing freezing up. As Nico has suggested, it definitely seems to be related to whatever sort of events you have configured in the form.

    This will require additional investigation, so I would recommend that you submit a ticket to our Support team who can help to move this process forward. We'll be sure to report any findings here in this thread so that other Community members can take advantage of that knowledge.

    Thank you, and have a great day!

    Phil

    0
  • Aaron Wong

    I've just created the ticket and attached my workflow to it. Will see what happens!

    Will having many forms in the workflow impact it? 

    Thanks,

    Aaron

    0
  • Phil MacIntyre

    Hi Aaron,

    That sounds great. Our Support team is very knowledgeable and can connect with the Products team as necessary. We'll get to the bottom of it.

    Re: multiple forms in a Workflow, I don't think it should. Once a form is done, we retain the values created by it until the Workflow runs to completion, but we shouldn't be retaining the elements once they've been disposed. We fairly regularly test for memory leaks (i.e., where actions or components continue to use CPU memory even after being cleaned up) and haven't seen anything recently around multiple forms.

    Cheers,

    Phil

    0
  • Phil MacIntyre

    A brief update on this:

    - the issue appears to be related to using Get Form Element Items from Collection activities for multiple form elements. If you use individual activities for each form element, the issue seems to go away

    - it appears to only affect iPads. iPhones, Android, and Windows devices are unaffected

    We now have a bug in our backlog with a reliable reproduction sample and will look to address it in a future release.

    Thank you for your patience,

    Phil

    0

Du måste logga in om du vill lämna en kommentar.