This is a best practices question, Should data be written to a data store after

I don’t think it is necessary to write to DB after every UI node. It would be purely on requirement. It is better to write after you have collected all data to avoid multiple DB interaction.

It would really depend on your overall application design. If you are reporting on the RDBMS data using a 3rd party tool or SAIL reports using queryrules/entity then you might want to consider writing after every UI node to ensure that the data is up to date. If the RDBMS is seen as the primary source of data then this is another good reason to consider multiple writes.

Great, thanks to you both.

From personal experience what I have found is that if the process is long running, so for example a case management style process you should do regular write downs. But if the process is short lived, then you can build the data in a CDT and the drop it in to the db at the end of the process instead.

Good to know, Thank you.

Apart from the asked question and mentioned explanation as you'r asking for best practice I would also like to add that if your application needs to write data to data store entity multiple times then a separate sub process should be maintained just for writing the data on database, its not a thumb rule but surely makes your process models more configurable.