In camunda, if a lot of data are associated with a task, should we try to capture the data in the task itself? or the data has to be stored in a separate table and use Camunda only to track the status?
For instance: In the below process, as part of registration, I want to capture (name, address, state, country, etc) then these data should be embedded somehow in camunda registration task itself? (or) a separate table to store the data?
In general, I would follow the advice from the post by @hassang that only the information that the process needs itself to correctly coordinate what’s going on should be added to the variables. I created a post a while ago that describes this: http://airquill.io/2014/06/29/storing-data-in-processes/ The basic idea behind this thinking is to keep the process lean and focussed and deal with all of the concerns of the domain it’s working with in the application itself.