We are trying to setup Appian application deployments through our release manage

Outside response: Eduardo Fuentes There's a script to import application under <APPIAN_HOME>\\_admin\\_scripts called import.bat|sh but it's a beta version which means is not documented but you can check its own documentation by running

import.bat|sh -help

I'm curious as to how people are managing versions of their Appian applications and the different components that make it up. Are you committing the Appian application zip file as a whole to the release management tool? Thanks.

Very good question. There was a good article in the old product documentation page: forum.appian.com/.../Change_and_Configuration_Management

We are currently using the method described there. So basically deploying everything in v1.0 of an application and only deploying the delta afterwards. Unless changes are getting to big in that case we would deploy the whole thing again.

errata: article is also in the current documentation / STAR methodology: forum.appian.com/.../Change_and_Configuration_Management.html

Thanks for the response. So what environment or version control system is the source of records (versions)? Is it the shared development environment, a stage environment? Im familiar with traditional version control and our Management and CM team want to version the Appian applications. I need to more concise answer for them. The documentation does a good job at describing the process but I seem to be missing the point of where version management is done. Thanks.

Version Management within the development environment can be done with the functionality you have in Appian anyways.

When we deploy our applications to a higher environment we submit only the delta packages to the version control system. So we submit initially packages like App1_v1.zip; then App1_v1HF1.zip etc.

This is definetely not an ideal way of handling this, but we haven't come up with a better idea of how to handle this yet. The main problem is definitely that the version control system doesn't know anymore to which initial version the hotfix belongs as the name is different.

Have noticed that the Change Management docs have changed a little over the versions (7.7 to 7.11) and if fact shows much less info in the newer version specifically around the "Subsequent Application Migrations" section. In 7.7 it talked about full vs patch and 7.11 only talks patch. Is Appian recommending going forward that is always use the patch approach?