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

John over 12 years ago

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...

Discussion posts and replies are publicly visible

Parents

0 John over 12 years ago

Changes as in bug fixes mainly, but could include other items. We do not currently change constants in production, so that's not too much of a concern for us. My main concern is really identifying what consists a process (application) and how to rebuild it or migrate it to another environment en masse.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 John over 12 years ago

Changes as in bug fixes mainly, but could include other items. We do not currently change constants in production, so that's not too much of a concern for us. My main concern is really identifying what consists a process (application) and how to rebuild it or migrate it to another environment en masse.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data