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 shelzle over 12 years ago

How is your organization set up? We have a team of project managers that manage our internal improvement projects. The resulting change requests are developed by a small team of process modellers who are also responsible for deployment, testing and so on. Administration is done by our IT dept. but only on an operational level regarding keeping Appian running, technical interfaces to other systems etc.

Keeping track of what belongs to an app can be hard as there are always common reused things and items that are not recognized by dependency analysis. Maybe you have an application package that mainly contains the user frontend (pages, navigation) and a hidden maintenance app that cumulates changes and is reset on deployment.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 shelzle over 12 years ago

How is your organization set up? We have a team of project managers that manage our internal improvement projects. The resulting change requests are developed by a small team of process modellers who are also responsible for deployment, testing and so on. Administration is done by our IT dept. but only on an operational level regarding keeping Appian running, technical interfaces to other systems etc.

Keeping track of what belongs to an app can be hard as there are always common reused things and items that are not recognized by dependency analysis. Maybe you have an application package that mainly contains the user frontend (pages, navigation) and a hidden maintenance app that cumulates changes and is reset on deployment.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data