Hi Nandika,
Activiti documentation doesn't mention about the CATEGORY_ column. But they
have provided a method to set values for the CATEGORY_ column.
In future they may use the column for different purposes or they may
deprecate this method.
Therefore as a safest option, we can use a new table
Hi All
We have started to work on storing the artifact related version information
in to process DB. Initially we are going to implement it to BPMN.
We have identified two implementable approaches.
1. We can use the internal available ACT_RE_DEPLOYMENT table's CATEGORY_
column to store the
Hi Firzhan,
Does activiti documentation documents the CATEGORY_ column as a not used
column. Otherwise there could be some usage of it, even though we have not
encountered it yet. If the documentation states that the column is not used
and is there for implementing extensions, then its fine to
+1 to remove storing versioning information storing from registry. The
method of making the registry read only for worker nodes has added
unnecessary complexity to bps clustering. It also has led to many support
issues due to wrong configurations. By storing the versioning data also in
the bps
Hi,
In business process server, artifacts are deployed with a version number.
In a clustered environment, in order to avoid the possibility of same
artifact having different version numbers assigned by both worker nodes and
master node, we have to make sure that only the master node is allowed
