Skip to main content
D
darend482717
March 18, 2026
Question

Version Control like Git?

  • March 18, 2026
  • 3 replies
  • 0 views

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!

    3 replies

    shubhama926776
    shubhama926776
    March 19, 2026

    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

    stefanhelzle0001
    stefanhelzle0001
    March 19, 2026

    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.

      ericc087568
      ericc087568
      March 26, 2026

      We're doing a half-way version with Azure Dev Ops pipelines which sticks items in repo.  Problems occur though if attempting to get back to point in time because of recordtypes / database and service dependencies / and pull request per user story became a nightmare with some items passing testing but not all, etc.  

      Terms & ConditionsAccessibility statement