The last post covered application upgrades. Today we'll dig into a few more features of a Fuji application including dependencies and uninstalling.
As you build and test your application, there's a little bit of platform logic that watches what you are doing and identifies dependent application packages that it can identify. I'm not sure of the exact logic but I know any script calls to tables outside your scope (that obviously have been granted access) will be captured by the system. I would have thought that adding a simple reference field to a table outside of your scope would have identified a dependencies but it doesn't appear that way (at least in patch 2 hf1). You can also manually add dependent packages from your application page if you know them and they haven't been captured.
Once an application is downloaded to a target instance, you can view the list of dependencies, although not really in a friendly fashion and there's no link to the plugin. But at least you can view the list.
If you attempt to install the application without having the required dependencies you will be alerted that the install cannot be completed. I would prefer the option to simply install the dependencies from this page but we'll have to wait for a future release for this one.
Once applications are installed there's an easy way to uninstall them if you decide for some reason it's not for you.
The multi-step confirmations makes it clear exactly what you are removing. You also have the option to keep the table structure and data if you wanted it for reporting or other reasons.
Even though the application is uninstalled it will still be re-installable from the list of applications downloaded to the instance.
Next in our "What's an app mini series" is identifying local changes to an application.