Version Control like Git?

Question

Hey all, new Appian developer here! From what I have learned so far, Appian dev teams don't usually follow the branch->merge workflow, but rather work inside the single dev environment. I have no problems with this system and think it is the ideal approach for 99% of cases. However, in a situation like a refactor, where you are changing some of the architecture and breaking a few parts of the system as a side effect, I can see how branching off to make these changes would be safer, cleaner, and not prohibit other developers who need to use the parts that are being changed.

Is there any version control (or hacky workaround) that could solve this in these rare situations? Thanks!

Shubham Aware · Answer

Appian lacks native Git branching - teams share one dev environment with object versioning. Workaround - Prefix-clone the objects being refactored (e.g., v2_myProcess), work on clones, swap references when done, delete old ones. For refactors, use AVM plugin

Stefan Helzle · Answer

IMHO the main reason for git is decentralized development in potentially large teams. 
 Development in Appian in centralized and in small teams, so I do not see any need. 
 When changing objects, I typically do not just change that one object, but follow the chain of dependencies and adjust them to work with the changes.