Process versions

danielg424213 said:

I have 3 doubts in Appian environment. Can you help me, please?

1. In Appian, can you work with branches associated with process versions, similar to GitHub?

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?

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?

Thanks in advance.

I’ve worked a bit with Appian, so here’s my take:

1. Branches like GitHub: Appian doesn’t have a traditional branching system like GitHub. You usually manage different versions of your objects (processes, interfaces, etc.) in environments (Dev, Test, Prod) and use versioning within the objects themselves. For true branching, people often export and manage multiple versions outside Appian or use separate environments.

2. Two versions running in production: Not exactly. In production, the latest published version of a process is what runs by default. You can’t natively “choose” between two versions for new instances. Some teams work around this by duplicating the process with a different name or using conditional logic to redirect flows, but it’s not built-in like Git branching.

   Hope that helps clarify things! Has anyone tried a workaround for running multiple versions simultaneously?

   My website: brainrot clicker

danielg424213 said:

I have 3 doubts in Appian environment. Can you help me, please?

1. In Appian, can you work with branches associated with process versions, similar to GitHub?

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?

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?

Thanks in advance.

I’ve worked a bit with Appian, so here’s my take:

1. Branches like GitHub: Appian doesn’t have a traditional branching system like GitHub. You usually manage different versions of your objects (processes, interfaces, etc.) in environments (Dev, Test, Prod) and use versioning within the objects themselves. For true branching, people often export and manage multiple versions outside Appian or use separate environments.

2. Two versions running in production: Not exactly. In production, the latest published version of a process is what runs by default. You can’t natively “choose” between two versions for new instances. Some teams work around this by duplicating the process with a different name or using conditional logic to redirect flows, but it’s not built-in like Git branching.

   Hope that helps clarify things! Has anyone tried a workaround for running multiple versions simultaneously?

   My website: brainrot clicker