Hello All, We are in need to change the Appian version from 7.4 to 16.1, ar

himanshun over 9 years ago

Hello All,
We are in need to change the Appian version from 7.4 to 16.1, are there any specific precautions which we have to take (like application and DB backup) also is there any functionality which might break while doing so and if yes is there any alternative to avoid the same. I know that the deprecated rules still continue to work in the higher environments however wanted to know for any other components like process models, records, reports etc.
Request you to suggest the points to remember while doing the migration.

Thank You

Discussion posts and replies are publicly visible

0 Eliot Gerson
Appian Employee
over 9 years ago

You should absolutely backup the environment before updating Appian; in fact, it's a requirement. Please carefully follow the instructions in the documentation. forum.appian.com/.../Upgrade_Guide.html
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jim Schweitzer
Certified Lead Developer
over 9 years ago

Always upgrade a QA environment first, and perform functional regression testing in that environment prior to upgrading production.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 vishnuv
A Score Level 1
over 9 years ago

Hi Eliot & Jims, wanted to check if any components break during migration from 7.4 to 16.1.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Jim Schweitzer
Certified Lead Developer
over 9 years ago

You should read the release notes in detail for every release between 7.5 and 16.1 and evaluate for your applications. It's rather hard to predict, though, which is why you need to just try and thoroughly regression test. I've seen AN-54003 which was changed in 7.5 break code from 7.3 for example. forum.appian.com/.../Appian_Release_Notes
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 narasimhaadityac
A Score Level 2
over 9 years ago

Hi Himanshu, as suggested by Jims we need to look at the release notes, specifically some of the things like, where local variables instantiated within the "with()" in the saveInto parameters of the buttons might not be giving errors in lower version but in higher versions it was mandated that they need to be instantiated in the load(). another one like using partials (_) in the save into parameters.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel