Application Packaging & Deployment| Appian 7.8 Is there any best

abhinavg over 9 years ago

Application Packaging & Deployment| Appian 7.8

Is there any best practices around the same topic..
We have an application being tested in QA environment but it's going under continuous iterations both ( design & business)

So when ever we push the new changes from Dev to QA, do we need to make new Application Patch sets and add only changes to QA or add the new changes to existing Application bundle already deployed to QA, and then redeploy the full application again even few Appian objects updated/added and rest Appian objects remains as earlier but will end up creating new versions for Appian objects which were never updated

Which one is the best approach and why ?

Thanks,
Abhinav

Discussion posts and replies are publicly visible

Parents

0 joel671 over 9 years ago

I personally would advice the first option. The main reason for this would be the more "versions" of running process can cause your execution engines to bloat. Therefore by only releasing what has changed keeps this under control. Another consideration is that it general is considerably quicker to patch rather than release a whole application particularly for large applications.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 joel671 over 9 years ago

I personally would advice the first option. The main reason for this would be the more "versions" of running process can cause your execution engines to bloat. Therefore by only releasing what has changed keeps this under control. Another consideration is that it general is considerably quicker to patch rather than release a whole application particularly for large applications.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data