Why [ Automation Version Management ] when appian is already having version control to their objects

RE: Why [ Automation Version Management ] when appian is already having version control to their objects

mayurm168 — Fri, 24 Aug 2018 05:21:05 GMT

Few more points I would like to add in answer.

As we are saving version of application now, we can literally rollback at any stage of development.
This means we can can change version of number of objects at one go if we save the application in version controller.
If user wishes to use previously suggested functionality then rather then changing version and keeping track of every single object it's always good to keep version of whole of the application at once.

Hope this justifies...!

RE: Why [ Automation Version Management ] when appian is already having version control to their objects

Shiva Valusa — Thu, 23 Aug 2018 07:08:46 GMT

Agree with Prateek,
As of now Appian maintains versions in object level but not applications level. And AFAIK when you are importing Application in GIT repository it maintains version of your whole application.

RE: Why [ Automation Version Management ] when appian is already having version control to their objects

PRATEEK BHATTI — Thu, 23 Aug 2018 06:22:21 GMT

Hi Bhargavi,

Appian maintains versions for Appian artifacts(Process models, rules etc) but it doesn't maintain versions on Application level as of know, however Appian has introduced Data server in 18.1 with the intention of maintaining application level versions as well but it is not in place right now. Here comes the need for Automated Version Controller like Git(which I have worked upon personally) where you can export the complete application in a form of zip file and attach that zip file in GIT repository link it with a tag id(Incremental no.) so that you can have complete information how,what and when the changes were made at application level because using Automated Version Controller you can maintain application level versioning explicitly.

Hope it helps!!