importing application to different version

Question

Hi, 
 we will not be able to upload the application if the destination environment has different version. 
 But during the upgrade of the appian version, all codes changes accordingly. 
 How this is happening and can we use that to import in that scenarios. 
 Thanks, 
 Seenivasagan

Amit Mishra · Answer

Hi Seenivasagan, 
 
We can import an application if destination environment has different version. But the environment should be higher version. You cannot import an application to lower version environment. 
Like, an application package of 18.1 or 18,2 can be imported to 18.3. But you cannot import 18.3 version application to 18.2 or lower version. Thanks

chandu · Answer

Hi Seenivasagan,

As part of the Upgrade, The code changes are done internally and we don't have any control on it.
We are not sure when those will be migrated, I believe that code changes will be done as part of new app server start.

So, raising a support ticket would be helpful so that we can get answers back from them.
BTW are you having any packages that contains huge number of files to be deployed from higher version to Lower version?
if so please refer to thread.
community.appian.com/.../appian-18-3-to-18-2-downgrade

ravalik · Answer

Hi Seenivasagan Perumalsamy , 
 
According to the Appian documentation, 
 
Application packages from an earlier version can be imported by later versions. Packages exported from later versions of Appian are not compatible for importing into prior versions. When exporting a rule or constant or integration the latest version is exported. On import, a new version of the rule or constant is created. 
 
If an imported object already exists in the destination environment (identified by a universally unique ID or "UUID") a new version is created – so long as versioning is supported for the object. 
 
When versioning is not supported for an object, the imported object overwrites the object in the destination environment and its properties.

Thanks, 
ravalik