Skip to main content

Hi

We have a customer which is complaining that the site access hour are not refreshed in mobile edge..

The scenario is at first the customer site has no access hour defined (for example), There is a service order assigned to a mobile technician. On his mobile device the technician can see that there is no access hour defined in the module site details / acess hours this is ok.

 

Then in the back office the Access hours are updated on the site

.This information is not pushed to the mobile device , even if a new service order for this site is assigned to the same technician.

is it normal ? 

thanks for your feedback

Christophe

 

Hi Christophe,

I just tried this on QAC and you are correct it does not automatically push the changed site details.

However, you can use the search option in the Site Details screen and do an Advanced Server Search.  Find the site after filling in the site criteria and select it.  You will then get a screen like the following:

 

Click Yes and the site details are refereshed.

Then the updated site details were shown in the record:

 

I suggest logging a ticket for this anyway as perhaps it should push automatically and it might not update as the site details record already exists in mobile.  This should be reviewed, however at least this way you can get the updated details down to the client.

 

Thanks Phil i will log a ticket, i was also think about changing the MOE -700 to pass it to 1 day (i will see with the customer if it’s also acceptable)

 

Christophe

Hi Christophe,

That is an option but of course won't help if the work order needs the site details same day.  At least with the search, it is updated definitely.

I still think this should be reviewed as there is an MOE option for a notification involving site changes in the SERVER MOE which the text implies it will still be pulled down to the device.

 

 

Hi Christophe,

I see this was fixed in our ticketing system and will be going through QA for the next SU release.

 

Hi @Phil Seifert 

I’m in the last version 15.4.8  and I have the same issue.
Do you know if the fix it’s OK , without any user action ?


Thanks and Regards

anthony

Hi Anthony,

It was not a back end solution, it was Mobile Edge.  I don’t know what version of Mobile Edge you tested against but according to the Mobile Edge Maintenance Release 15.4.12.0.pdf it was fixed with this version of Mobile Edge.

 

This will require reinitialization of the mobile client due to the Mobile Edge version change.

 

Reply


Terms & ConditionsCookie settings