Upgrading Apps and managing conflicts

[xMTinkerer]

Hey guys,

    I'm wondering what others experiences are when a customer does an upgrade to a new version of the app. We recently released a new version and I got to watch a customer go through the process of doing the actual upgrade. They were totally blown away by how easy it was and how it was rather safe because nothing was overwritten. We don't protect or make readonly any of the Business Rules or Script Includes in our app so customers can and do make changes in accordance with their business use cases.

However, one thing I found rather lacking was a way to see in one place all of the collisions. For example, if we have 5 Script Includes and 3 business rules as part of the app. The customer then makes changes to 2 Business Rules and a Script Include, then with the new version, we have to update all 5 Script Includes and all 3 Business Rules. As it is now, after the upgrade, the customer must go into each of the 8 records and visually inspect the Revision History for any that weren't upgraded.

So, I'm curious how you guys handle the following:

1. Is there a central place to see all the revisions needing to be reviewed?
2. Does the "compare" work for you guys? When I check the box next to the current and one other revision item, then select the "Compare" option from the actions drop down, nothing happens... no form refresh, no new dialog... am I missing something?
3. How do you test or document the upgrade? As far as I can tell, we can't install a previous version to our ven instances, so we really only have one shot to test or document the upgrade.

I'd be interested in your feedback on how you handle upgrades from apps in the store.

Thanks!

  --- Travis

[The SN Nerd]

I'm currently having issues where Forms and Form Sections are not being applied to Fuji instances.

I'll be sure to check out the upgrade history.

EDIT

It looks like there is a bug in the Upgrade History counter.

It says 0 skipped, but on closer inspection there were 38!