Process versions

Hi Daniel

Thanks for the questions. Appian does not have anything like branching and merging as you might find in other languages or platforms. It is a 'trunk-based' development environment so there's only ever one active version of any object type. 

If you want two 'versions' of a process running in an environment you'd have to create a 'clone' so that the two process models were effectively independently managed objects.

The last question suggests that you're conceptualizing the implementation of Appian applications as 'long-running process' paradigms. This is absolutely not the way to think of Appian apps. There are some very good reasons to design and implement Appian as 'short running procedures' that manage the state of the data, where the data is conceptualized as 'records'. Records are the key entities that make up your data model that underpins your application. If there's a 'process' anywhere in Appian it's a conceptual one where the state of the records governs, via rules, what procedure(s) are enabled/disabled at any point in time. Think more about a state-engine paradigm than a process paradigm.

1. In Appian, can you work with branches associated with process versions, similar to GitHub? No, Appian doesnt work in that way

2. Is it possible to have two versions of the same process running in production and choose at any time which one the application should use? No, in that case, you must have two copies of the process with different names.

3. If a new version of a process is deployed to production, can migrations be performed for the processes that are active at that moment?  If you want to migrate your process from one version to a newer one... you must finish one and create an instance of the new process from scratch, using thee same context.