I have just taken over as the main Appian administrator for our organization and

I have just taken over as the main Appian administrator for our organization and am thinking there should be a "better way" to how we are handling environment migration. Does anyone have any best-practice advice for migrating from dev->test->production? The concerns I have are mainly about keeping track of what packages have effected what processes as well as backing out changes. Is it better to always move an entire Application and therefore update the single application definition over time? Should we have application fixes (minor versions) and therefore falling back to a previous version would require a lot of hunting to previous packages.

Any advice is greatly appreciated!
---John...

OriginalPostID-63953

OriginalPostID-63953

  Discussion posts and replies are publicly visible

Parents
  • We have 3 main groups. The infrastructure group which looks after the servers/platform as well as performs the UAT and Produciton migration of packages. The applications group which performs the L2/L3 troubleshooting and bug fixes. The development group which creates new processes and large-scale changes. We do have a couple sets of "common" elements which are packaged separate from each of the major applications. Each process (or group of processes really) are considered separate applications.
Reply
  • We have 3 main groups. The infrastructure group which looks after the servers/platform as well as performs the UAT and Produciton migration of packages. The applications group which performs the L2/L3 troubleshooting and bug fixes. The development group which creates new processes and large-scale changes. We do have a couple sets of "common" elements which are packaged separate from each of the major applications. Each process (or group of processes really) are considered separate applications.
Children
No Data