Solved

Maintenance Survey (eForm) Performance

  • 27 April 2022
  • 7 replies
  • 282 views

Userlevel 5
Badge +14

Has anyone had any performance issues with Maintenance Surveys (eforms) for mWO Service 10.  We have some survey that take well over 60 seconds just to open and this was on a windows client.  We are using mWO Service 10 v1.6

icon

Best answer by Bandula 28 April 2022, 17:24

View original

7 replies

Userlevel 6
Badge +12

Hi,

It could be a delay when it got very long survey or many multiple child surveys connected. 

Split into separate surveys may help. 

Userlevel 5
Badge +14

Hi,

It could be a delay when it got very long survey or many multiple child surveys connected. 

Split into separate surveys may help. 

Thanks @Bandula, I think it was faster when we had the child surveys.   We can’t split this surveys up, business won’t accept that.  Is there anything else to help speed these up?  It was pretty bad doing a demo in front of stakeholders.  

Userlevel 6
Badge +12

All connected child surveys will load internally with the main survey before the start. But it we have multiple surveys it load separately after each one.  

Can you please share 

  • No of questions in each survey. 
  • No of child surveys  
  • Types of survey ( Employee/Object/Task ..) 
Userlevel 5
Badge +14

All connected child surveys will load internally with the main survey before the start. But it we have multiple surveys it load separately after each one.  

Can you please share 

  • No of questions in each survey. 
  • No of child surveys  
  • Types of survey ( Employee/Object/Task ..) 

We removed child survey’s, so our average surveys have about 100 questions

Type of Survey is a Task.

 

Did more testing today on a different platform, and on the Android the performance is about 1000x better.  When we did our demo we used the windows platform which was horrible.  

Userlevel 6
Badge +12

We see different performances in different platforms since we have 3 separate apps for each platform. 100 questions are still a very large no for a mobile app survey. 

Is this a realistic scenario to have 100+ questions to answer by field user ? 

If that the case i would suggest to split into 3 surveys and order them using rank value.

 

Userlevel 5
Badge +14

We see different performances in different platforms since we have 3 separate apps for each platform. 100 questions are still a very large no for a mobile app survey. 

Is this a realistic scenario to have 100+ questions to answer by field user ? 

If that the case i would suggest to split into 3 surveys and order them using rank value.

 

Thanks, and yes 100+ survey questions is the norm for Generator Service.  We have a lot of customer specific forms (Customer required data capture) that need to be filled out.  Our solution is to capture all data in the eform.  Then we have a custom event to run the relevant SSRS report and auto attach it to the work task.  That in turn uploads to mobile (sync entity schedule has changed to 3 mins).  That way the technician can print and leave formatted paperwork with customer if needed.

 

Average survey is 150 questions.  

 

I am quite certain customer will not want to split the survey from 1 to many.  They are already saying it feels they’re taking a step backwards from their current system to IFS with certain limitations.

Userlevel 6
Badge +12

Ok, in that case you may report an issue though support channel. 

Reply