Dynamic Lockdown - Don't display icon if app doesn't exit

Solved
CR
Chris R.
SkyBitz - End User

Hi,

I am playing with the dynamic template in hopes of coming up with a solution to resolve an issue we are having with kiosks at the moment.  We are actively migrating our devices from one version of our application to a newer release which have different package IDs.  It's become very cumbersome to build and maintain 2 different profiles per customer device grouping and swapping them once we know an app has been updated.  If the profile swap doesn't happen or if we don't know a customer has migrated apps, they will then have a kiosk with no apps present until someone manually unassigns/assigns the profiles properly.

I was hoping to utilize the dynamic HTML template and tweek it where I could add both application package IDs into the lockdown and the template would only display a link to an app if it actually exists on the device.

I wasn't sure if anyone had experimented with a similar solution or had any other ideas. 

Thanks

3 years ago
Android
ANSWERS
RC
Raymond Chan Diamond Contributor
3 years ago

If an app is not installed, the app icon resource of course cannot be extracted, and therefore no kiosk item icon shown in the MobiControl kiosk.

Since only one of the apps is supposed to be installed on each targeted device,  the simplest approach is to use a script:// kiosk item instead of the usual launch://.  The script, say app1.cmd, should attempt to start both apps, e.g.

  start  com.abc.app1

  start  com.abc.app1_1new

The warning/error message associated with launching attempt of the missing app will not be visible to the device end-user.  There might be some small launching time delay if it is the second app that is on the device, but this approach is much simpler than using multiple profiles, multiple device sub-groups, etc.   A custom image, possibly extracted manually from either of the original app apk, has to be added in the configuration of the script kiosk item.

This approach might have glitches if your app design or usage requires you to use launchalways:// or other variants of launch:// in your original kiosk configuration.

Solution
CR
Chris R.
3 years ago

That's an interesting approach.  I'll test this out today and see how it works for us.  Our apps are typically just launch:// so I think that would be OK.  I assume I'll have to upload an app icon in this case.

MD
Matt Dermody Diamond Contributor
3 years ago

Linking to a script in the lockdown also requires you to first create a .cmd file containing the scripting that you want and to then place that script onto the device via either Package or File Sync. 

CR
Chris R.
3 years ago

I suppose I could have 2 profiles with filters for each app bundle ID.  I assume once an app is uninstalled and the new app is installed, a device check-in would re-apply the proper profile based on the installed application. 

I don't love this solution by default as I already have 300+ profiles.  Anything I can do to limit that and not add more would be preferred.  This would require adding an additional 70-80 profiles.

K
KCMOD@SOTI
3 years ago

Hello Chris,

Thank you for posting on SOTI Central!

I would like to follow up on this post and ask if Raymond's and Matt's advise helped to answer your question?

If yes, please mark this post as solutioned.

If you have any other questions, please let us know.

Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

CR
Chris R.
3 years ago

I created a .cmd file with the scripts and sent it out to the devices with a package.  Updating the lock down item to custom and calling that script does work.  Closing post.