How are your Document Classes organized and which ones are being made accessible for MWO? You can control this here: Document Classes (ifs.com)

Cheers

James

Hi James,

Thanks for your reply.

We use FTP repository to store all our IFS documents, and all document classes are all within one location. 

Yes we use the Touch App→Document Class screen already to define which are mobile document class etc. 

As stated above, we are sending lots of documents to engineers devices and they are either not looking at them or not aware if a crucial document has been updated which means they should read it.

We just see high sync times for doc specific entities and wanted to reduce this to avoid delays and timeouts.

Thanks

Is “Push To Mobile” enabled in Touch App → Document Class? If the engineers are not reading them then I suggest this is disabled to cut down on downloading of documents. This will then only happen if the engineer requests to download a particular document

Cheers

James

Yes “Push to Mobile” is enabled for all those document classes that have “Mobile Document Class” ticked. 

If we untick this field, I assume those documents attached to the associated work orders/tasks would not be sent to the mobile device. 

We still need documents to be sent to devices; so it is not a simple on/off situation. 

The issue is that the documents probably should be read, but as they go back to the same building/object than re-reading docs related to that are seen as unnecessary unless there is a Health&Safety implication or an update to these documents.

Disabling “Push To Mobile” does not mean the document is not available to the technician, it simply means it will be downloaded when the engineer requests to view the document. Rather than downloading in advance.

You could trigger an alert message direct to the engineer via SMS or Push Notification informing them of the new revision or add a custom field to the Work Oder informing them a new revision of the document exists and ask them to read it.

Cheers

James