https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?action=history&feed=atom&title=EST_350225_JBG_Remote_application_updates 2026-07-01T21:45:47Z Revision history for this page on the wiki MediaWiki 1.39.8 https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=EST_350225_JBG_Remote_application_updates&diff=5860&oldid=prev 2018-05-01T08:39:40Z

<p>v0.1 - Initial Draft</p> <p><b>New page</b></p><div>{{Template:Estimate<br /> |Supimix_Client_Code=JBG<br /> |Supimix_Project_Code=DEV<br /> |Supimix_Site_Code=DEV<br /> |Supimix_Client_Reference=&amp;nbsp;<br /> |Supimix_Number=350225<br /> |The_version_of_the_document=0.1<br /> |Your_Name=A N Walker<br /> |Supimix_PO_Reference=&amp;nbsp;<br /> |Supimix_Priority=3<br /> |Date_(DD/MM/YY)=1/5/18<br /> |Clients_Customer=Oak Furnitureland<br /> |System_Version_being_changed=4.X<br /> |Client_Request=A method is required to allow the mobile application to be updated in the field. MDM is not possible due to the old version of Android on the M3 SM10, so options being considered are Google Play (hosted by JB Global) or the application itself updating - but this needs to be verified to confirm that the locking software does not prevent this (OBS have a device which can be used to check this)<br /> |OBS_Solution={{Note}} Hosting under Google Play as a separate bespoke application is not the recommended solution, due to the continued cost accrued for each ''CALIDUS'' ePOD mobile device application release built by OBS Logistics.<br /> <br /> <br /> {{Note}} The process below has been confirmed as working on Android mobile devices from version 4 onward. It is not known whether this would work on a mobile device locked by the client's device locking software. In order to test this, a prototype application will be required to be built, along with familiarisation with the locking software used by the client. Time for this is not included in this estimate and would be changed T&amp;M, expected to be up to 2 days effort.<br /> <br /> <br /> The mobile device application will be modified to check the latest version of the application available at the point of logging on to the system.<br /> <br /> If the application hosted for the customer is a later version than the version running on the device, the application will ask the user whether this should be downloaded. Note: If the version is marked as required, this step will be skipped and the device will enforce downloading of the new version.<br /> <br /> The device will show progress of the download, and then will trigger the installation process for the new version before exiting the application.<br /> <br /> <br /> {{Note}} If the user were to cancel the installation of the new version, upon restart of the application the process above will be followed again, either asking for permission or enforcing the download and installation of the new version.<br /> <br /> {{Note}} In order to allow installation from file, the device must be configured to allow installation of apps from Unknown Sources. The exact process for achieving this differs with Android versions and models.<br /> <br /> <br /> This change will be completed in the latest version (V4) of the ''CALIDUS'' ePOD application.<br /> |Requirements_Days=0<br /> |Estimation_Days=0.25<br /> |Functional_Specification_Days=0.5<br /> |Technical_Specification_Days=0<br /> |Development_Days=2.25<br /> |Testing_and_Release_Days=0.5<br /> |Implementation_Days=0.25<br /> |Project_Management_Days=0.25<br /> |Year=2018<br /> |Free_Of_Charge=N<br /> }}</div>

Anw