As the world changes your processes must change with it. 


It is essential to keep you process applications up to date as your organisation evolves.  

In this article we will describe Bariums best practice when it comes to upgrading and maintaining your processes and applications.  


Upgrades are done in two parts: Process model updates and form changes. These work a little bit different so let us take you through it.


Process model updates

When you want to make changes to a process model, you can do so by using the modelers built in version control. You can read more about process model version control here. Updating your process model means you simply redraw parts of your process in the modeling tool, maybe adding new roles or new tasks, gateways and events and then deploying that updated version which then upgrades your application allowing any newly created instances to run on that new version.


Form changes

When it comes to making changes in your E-forms there are some other things to note which differs from how the process modeler works. The main difference is that the form editor does not have a version handler or an auto save function. This means that any changes you make and save will instantaneously affect all running instances regardless of what process model version they are running on (given that those versions use the form template you made changes to).


NOTE: We do store each save you make in a version logg in our database. So if you have encounter an error within the form template or accidentally erased over your form definition. You can contact Barium Support and they will help you restore the older version of your form template. Note also that any changes you forget to save will be lost so be sure to press save button frequently.


- I want to make form changes that affect previously started instances

If this is what you want, simply make the changes in your form and save them. Any new fields added will be added to your forms.

WARNING: If you add a field that is mandatory to fill out but is only visible for example at the start of the process, any instances which have progressed past the start won't be able to complete tasks as they have a hidden mandatory field. For this situation, use the attribute "allowBlankInViewmodes" and list all the viewmodes in which that field will be hidden. You can read more about viewmodes here.


- I want to make form changes that don't affect previously started instances

In order to make form changes that don't affect already running processes follow the following steps to create a manual version handling of your form templates.

  • In the process modeler asset browser, double click your current form template and change its name from "Template Name" to "Template Name 1.0".
  • Create a new form template and name it "Template Name 2.0". Copy the form definition from Template Name 1.0.
  • Make the new changes to the "template 2.0" and save the form.
  • In the process right click on form template in the modelling tool and click on "Do not use".
  • Click on the field "Choose a template or create new" and choose "Internal form 2.0"


  • Publish and deploy the process.