You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of serialisation/deserialisation is not really useful if you want to save process instances in a database. You can't store them serialised because you can't do any kind of report on the process data not to mention sorting/filtering data in a work list..
In a database one would save the following data for a ProcessInstance:
id, name, idProcessDefinitionVersion, process data
all tokens available
all work items available and the activities they are linked to.
all sub-process instances and the activities they are linked to (this is not implemented yet)
So the ProcessInstance class could be modified to serialise/deserialise only the data described above. Anyone agrees to this? Anyone working on this already?
The text was updated successfully, but these errors were encountered:
The current implementation of serialisation/deserialisation is not really useful if you want to save process instances in a database. You can't store them serialised because you can't do any kind of report on the process data not to mention sorting/filtering data in a work list..
In a database one would save the following data for a ProcessInstance:
So the ProcessInstance class could be modified to serialise/deserialise only the data described above. Anyone agrees to this? Anyone working on this already?
The text was updated successfully, but these errors were encountered: