Hi, we're just in the process of upgrading to Appian 7.9. The bes

Yep - it's basically the same, and I expected something a little more elegant as you do.

It is, of course, possible to put everything in one application and generate the patches, but there's no historical record of the patches you create unless you export them to external version control, and even then there's not a good way of finding out what that particular patch contains.

For example, if you have a patch deployment that consists of 50 objects, you'd add those 50 objects to a patch, export the patch, and inspect it on the new system. Let's say you have missed a dependency and the patch should have been 51 objects rather than 50; you'll have to recreate the patch by manually adding all 51 objects to a new patch, because when you export the application patch, the content of that patch is cleared.

For us, adding every required object to a patch each time the above happened was impractical, so we have a top level application - "My App" - containing everything, then an application the "next" version of that application - let's call it "My App 1.1", which is a subset of the top level application and would contain, for example, the 50 objects mentioned above. When testing is in progress we'll often want to issue small updates to one or two objects in the "My App 1.1" application after that application has initially been deployed to the test environment - it's there we'd use the patch functionality.

Yep - it's basically the same, and I expected something a little more elegant as you do.

It is, of course, possible to put everything in one application and generate the patches, but there's no historical record of the patches you create unless you export them to external version control, and even then there's not a good way of finding out what that particular patch contains.

For example, if you have a patch deployment that consists of 50 objects, you'd add those 50 objects to a patch, export the patch, and inspect it on the new system. Let's say you have missed a dependency and the patch should have been 51 objects rather than 50; you'll have to recreate the patch by manually adding all 51 objects to a new patch, because when you export the application patch, the content of that patch is cleared.

For us, adding every required object to a patch each time the above happened was impractical, so we have a top level application - "My App" - containing everything, then an application the "next" version of that application - let's call it "My App 1.1", which is a subset of the top level application and would contain, for example, the 50 objects mentioned above. When testing is in progress we'll often want to issue small updates to one or two objects in the "My App 1.1" application after that application has initially been deployed to the test environment - it's there we'd use the patch functionality.